git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: git-feed-mail-list.sh
Date: Tue, 09 May 2006 01:28:42 +0100	[thread overview]
Message-ID: <1147134522.2694.45.camel@shinybook.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0605081715270.3718@g5.osdl.org>

On Mon, 2006-05-08 at 17:19 -0700, Linus Torvalds wrote:
> Well, you might choose to just not use "git-cat-file commit" but instead 
> ask git to format the thing for you.
> 
> Ie you could probably more easily parse the data from something like
> 
> 	git show -B --patch-with-stat --pretty=fuller $commit
> 
> instead of using "git-cat-file commit $commit" and generating the stat and 
> diff manually.
> 
> That way you get the dates etc pretty-printed for you by git.

Aha, thanks. Git has learned to do a lot more since I first started
hacking up a copy of git-log.sh to feed the mailing lists, and it even
had to walk the commit tree manually :)

The output of (the undocumented) '--pretty=fuller' is probably good
enough that I can just feed the mailing list with it directly. I think I
have to add the commit and the parent manually, but that's easy enough
to do -- the commit is obviously known, and the parent is just
$(git-rev-parse $commit^1).

Anyone got any objections to switching the kernel git-commits-* lists to
this format?

-- 
dwmw2

  reply	other threads:[~2006-05-09  0:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:48 git-feed-mail-list.sh David Woodhouse
2006-05-04  4:35 ` git-feed-mail-list.sh Junio C Hamano
2006-05-04  5:16   ` git-feed-mail-list.sh Junio C Hamano
2006-05-08 23:44   ` git-feed-mail-list.sh David Woodhouse
2006-05-09  0:19     ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  0:28       ` David Woodhouse [this message]
2006-05-09  0:36         ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  0:53           ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  0:57             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  0:59               ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  0:45         ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  1:01           ` git-feed-mail-list.sh David Woodhouse
2006-05-09  1:05             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:12               ` git-feed-mail-list.sh David Woodhouse
2006-05-10  8:49                 ` git-feed-mail-list.sh Martin Mares
2006-05-09  1:27             ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  0:55       ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  1:03         ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:09           ` git-feed-mail-list.sh Bertrand Jacquin
2006-05-09  2:41             ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  3:06               ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  7:32                 ` git-feed-mail-list.sh Junio C Hamano
2006-05-09  1:18         ` git-feed-mail-list.sh Linus Torvalds
2006-05-09  7:15           ` git-feed-mail-list.sh Junio C Hamano

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=1147134522.2694.45.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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).