9 Dec
2013
9 Dec
'13
8:23 p.m.
On 12/09/2013 08:53 PM, Andrey Semashev wrote:
On Monday 09 December 2013 20:44:58 Bjørn Roald wrote:
On 12/09/2013 08:41 PM, Andrey Semashev wrote:
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...
right, my point is that there is a difference between these two options, and we should use -d. The -D option is for when you really mean to get rid of what the branch contain, not just the branch ref. -- Bjørn