Re: [PATCH 2/2] branch: protect local upstreams from -d
Show 11 quoted lines
> } Do we also need the same safety around "git branch -d feature1" by
> } the way? The "-d" option with safety checks the same "is feature1
> } already merged (to its upstream)?" condition, so it can protect the
> } feature2 branch the same way, by saying either "oops, you cannot
> } delete feature1 because you still have other branches like feature2
> } that depend on it", or "ok, featur2 used to depend on feature1, but
> } because we are deleting feature1 based on it being in origin/master,
> } we will make feature2 depend on origin/master from now on".
> }
>
> Harald, perhaps that's the passage you thought of?
Yes, exactly. Thanks for finding it!
Harald