git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Philip Oakley <philipoakley@iee.org>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: Suggestions for "What's cooking"
Date: Thu, 13 Sep 2012 09:09:20 +0200	[thread overview]
Message-ID: <505186A0.40500@alum.mit.edu> (raw)
In-Reply-To: <A7A1DB46082142E683753CFBC0A22A6B@PhilipOakley>

On 09/13/2012 12:49 AM, Philip Oakley wrote:
> My comment, as a simple reader, is that I misread the order of the 
> items, in that I miss-associate the description paragraph with the * 
> title _below_. That is, I see the description first and then read on...
> 
> Thinking about it, if the description paragraph was indented by one 
> space then the * title  would create that obvious content indent that (I 
> am) would be expected.

+1.  When I started reading the "What's cooking", I found it hard to
tell/remember whether text comments apply to the list of patches above
them or below them.  If you don't want to make bigger changes to the
format, then even an extra blank line between the section about each
patch series would remove the ambiguity.

Otherwise, I think that "What's cooking" emails are a great service that
you provide to the community.  They help mitigate the inconvenience of
using emails rather than pull requests for exchanging and managing
patches :-)

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  parent reply	other threads:[~2012-09-13  7:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 23:55 What's cooking in git.git (Sep 2012, #03; Mon, 10) Junio C Hamano
2012-09-11 18:34 ` [PATCH v3] Teach rm to remove submodules unless they contain a git directory Jens Lehmann
2012-09-11 19:41   ` Junio C Hamano
2012-09-12 19:21     ` Suggestions for "What's cooking" Jens Lehmann
2012-09-12 19:37       ` Jeff King
2012-09-12 20:08       ` Dan Johnson
2012-09-12 21:49         ` Junio C Hamano
2012-09-12 22:49       ` Philip Oakley
2012-09-13  5:14         ` Andrew Ardill
2012-09-13 18:06           ` Junio C Hamano
2012-09-14  2:11             ` Andrew Ardill
2012-09-14  2:29               ` Junio C Hamano
2012-09-14  3:58                 ` Andrew Ardill
2012-09-14  4:24                   ` Junio C Hamano
2012-09-14  6:00                 ` Philip Oakley
2012-09-13  7:09         ` Michael Haggerty [this message]
2012-09-13  7:21         ` Philip Oakley
2012-09-13 15:09           ` Junio C Hamano
2012-09-14  4:47             ` Junio C Hamano
2012-09-14  7:26               ` Michael Haggerty
2012-09-14 20:20               ` Philip Oakley
2012-09-12 19:24     ` [PATCH v3] Teach rm to remove submodules unless they contain a git directory Jens Lehmann

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=505186A0.40500@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=philipoakley@iee.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).