From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Git, ding-cvslog (gmane.emacs.gnus.cvs), ding-patches (gmane.emacs.gnus.commits)
Date: Thu, 02 Sep 2010 16:28:35 +0200 [thread overview]
Message-ID: <m362yojk30.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <8762yo72eb.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> It was intentional: I think it's better to see what commits are
> summarized in the message and the revision IDs are very useful if you
> plan to do anything beyond a quick review.
But do they need to be at the top? They're not very human-readable...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-02 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 7:44 Reiner Steib
2010-09-01 11:18 ` Ted Zlatanov
2010-09-01 11:21 ` Ted Zlatanov
2010-09-01 14:36 ` Jason L Tibbitts III
2010-09-01 20:22 ` Adam Sjøgren
2010-09-01 20:28 ` Lars Magne Ingebrigtsen
2010-09-02 2:42 ` Ted Zlatanov
2010-09-02 2:57 ` Lars Magne Ingebrigtsen
2010-09-02 10:05 ` Ted Zlatanov
2010-09-02 10:55 ` Adam Sjøgren
2010-09-02 12:31 ` Ted Zlatanov
2010-09-02 14:28 ` Lars Magne Ingebrigtsen [this message]
2010-09-01 20:30 ` Ted Zlatanov
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=m362yojk30.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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).