Re: Suggestions for "What's cooking"
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Sep 14, 2012, 06:00 UTC
- Message-ID
- <03339FB2E0624FCA858255742B9CA7FD@PhilipOakley>
- In-Reply-To
- <7vboh99w1z.fsf@alter.siamese.dyndns.org>
From: "Junio C Hamano" <gitster@pobox.com> Sent: Friday, September 14, 2012 3:29 AM
Show 38 quoted lines
> Andrew Ardill <andrew.ardill@gmail.com> writes: > >> On 14 September 2012 04:06, Junio C Hamano <gitster@pobox.com> wrote: >>> Andrew Ardill <andrew.ardill@gmail.com> writes: >>> >>>> <short-branch-description> >>>> <long-branch-description> >>>> <notes> >>>> <next-steps> >>>> * <branch-name> (<creation-date>) <number-of-commits> >>>> (<merge-status>) >>>> [list-of-commits] >>>> (<branch-usage>) >>> >>> I do not see how it makes any sense to have the "This is where the >>> section begins with, and its name is this" line in the middle of a >>> block indented in such a way. Care to explain? >> >> I'm not quite sure what aspect you are referring to,... > > Just this part, as I do not have much time. Here is your reordered > one I will reject: > > A > jc/maint-blame-no-such-path > > "git blame MAKEFILE" run in a history that has "Makefile" but > not > > "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got > > confused on a case insensitive filesystem. > > > B > * jc/maint-blame-no-such-path (2012-09-10) 1 commit > > - blame $path: avoid getting fooled by case insensitive > filesystems > > I was noting that B which *is* formatted as a header line (it EVEN > has a leading asterisk to make it clear that it begins something > new) is in the middle, and you added a redundant A that is not even > marked clearly as a header line. >
Are we all working with Black text on a White background? (or is it vice versa) as this changes which bits of emphasis the eye will pick up. I'm reading the emails as black text against a white background.
I find that for black text, in a block format, that one does not notice any special inital character, such as the '*', when it is part of a rectangular block. In fact I feel I tend to, if anything, down grade text begining with special characters as being bullet points below some main block text. Hence my suggestion to have either a visual break (extra line above), or a block indent (extra left hand space).
Changing the contrast to white text on a black background totally changes what the eye/brain will see/notice [$dayjob is electro-optic vision systems where contrast inversion is a standard requirement for that reason]. It maybe that we are seeing different personal effects because of our set-ups.