Re: [boost] A proposal for superproject structure and testing

Subject: Re: [boost] A proposal for superproject structure and testing
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-12-09 14:53:52

On Monday 09 December 2013 20:44:58 Bjørn Roald wrote:
> On 12/09/2013 08:41 PM, Andrey Semashev wrote:
> > On Monday 09 December 2013 19:29:59 Alexander Lamaison wrote:
> >> Vladimir Prus <ghost_at_[hidden]> writes:
> >>> On 09.12.2013 21:17, Alexander Lamaison wrote:
> >>>> Because, if so, that's not possible with git.  Branches are just
> >>>> nicknames for particular commits.  They can come and go pretty much as
> >>>> they please without disrupting other things.  Submodules reference a
> >>>> _commit_  and the commits remain in the repository regardless of what
> >>>> happens to the branches.
> >>> 
> >>> Then what does 'git gc' do?
> >> 
> >> Good point.  I forgot about this.  So, in general, the referenced
> >> submodule needs to include the commit in _some_ branch for the
> >> superproject to definitely reference a valid commit.
> >> 
> >> However, I think the discussion was about a commit already merged to the
> >> submodule's master branch, so gc won't touch it.
> > 
> > Not necessarily. In my example a boost release (i.e. a tagged commit to
> > the
> > superproject's master) references a commit in a submodule branch that is
> > neither develop nor master. That branch may never be merged to develop or
> > master.
> 
> There is a reason
> 
> git branch -d release-1.2.3
> 
> will fail with an error if the branch you attempt to delete is not fully
> merged.

There is also git branch -D...