Re: [PATCH v14 4/6] branch: add --prune-merged <branch>
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 8 quoted lines
> I was thinking that if I have feature1 with upstream origin/master and
> feature2 with upstream feautre1, then once feature1 is merged I'd still
> like "git log @{u}.." and "git rebase" without an explicit upstream to
> work when feature2 is checked out. If "git branch --prune-merged
> origin/master" deletes feautre1 then those commands stop working. Maybe
> it would be sensible to update feature2's upstream once feature1 is
> merged (which I think is what you're saying above) but do we really want
> to force the user to do that by deleting feature1?Ahh, reference with @{upstream}. Yeah, that _does_ make sense.