From: Junio C Hamano <gitster@pobox.com>
To: "Avery Pennarun" <apenwarr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Reformat "your branch has diverged..." lines to reduce line length.
Date: Wed, 16 Jul 2008 15:03:16 -0700 [thread overview]
Message-ID: <7v3am9pjvf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <32541b130807161327k17f3a58ay5ab2da75963a2d50@mail.gmail.com> (Avery Pennarun's message of "Wed, 16 Jul 2008 16:27:15 -0400")
"Avery Pennarun" <apenwarr@gmail.com> writes:
>> Your branch is ahead of 'origin/add-chickens2' by 21 commits.
>>
>> Your branch is behind 'origin/add-chickens2' by 1 commit.
>>
>> Your branch and 'origin/add-chickens2' have diverged, and have
>> 21 and 1 different commit(s) each, respectively.
>>
>> I moved "respectively" so that the variable parts will come close to the
>> beginning of physical line.
>
> Well, the fact that the number of commits is "variable" isn't so
> important, unless you start diverging by 1e9 commits or something :)
No, no, no. The point is not about keeping it on screen when "less -S"
chops at the right end. The point is to limit eye-movement of the user;
i.e. presenting important information consistently at around the same
column, closer to the left edge. Probably the line break should be before
"and have" to make it even easier to read.
>> Your branch and 'origin/add-chickens2' have diverged,
>> and have 21 and 1 different commit(s) each, respectively.
> Alternatively, your rephrasing above made me think of the idea of just
> printing *both* of the first two messages in the "diverging" case.
I do not think it is such a good idea --- we invite silly comments like
"You say X is ahead of Y, and X is behind of Y, which is true?".
> Please let me know if you want me to resubmit the patch with your
> suggestions or whether you'll handle it. I'm still a little vague on
> the exact patch approval process.
It is very much more "consensus building" than "approval", and at this
point we wait for a day or two to see if people come up with even better
alternatives. Just be kind enough to prod me if I forget after a few
days, though ;-)
prev parent reply other threads:[~2008-07-16 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 19:19 [PATCH] Reformat "your branch has diverged..." lines to reduce line length Avery Pennarun
2008-07-16 19:48 ` Junio C Hamano
2008-07-16 20:27 ` Avery Pennarun
2008-07-16 22:03 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v3am9pjvf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).