Re: Minor(?) usability issue with branch.<name>.pushRemote
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 12, 2018, 09:48 UTC
- Message-ID
- <xmqqh8fjhy8k.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <871s6n43ng.fsf@javad.com>
Sergey Organov <sorganov@gmail.com> writes:
Show 5 quoted lines
> So, finally, it's 'branch.linux.pushremote' that is the "offender". > > Looks like both 'git status' and 'git branch -vv' should somehow learn > about 'branch.<name>.pushremote' feature so that their > output/suggestions make more sense?
Doesn't "ahead of X by N" mean "you forked from X and built N commits on top", not "you have N commits that is not in X which is where you would push to"?