public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"David S. Miller" <davem@davemloft.net>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bk commits and dates
Date: Thu, 10 Mar 2005 07:11:45 -0700	[thread overview]
Message-ID: <1110463905.4026.11.camel@localhost.localdomain> (raw)
In-Reply-To: <422FE571.7010101@pobox.com>

On Thu, 2005-03-10 at 01:13 -0500, Jeff Garzik wrote:
> Speaking strictly in terms of implementation, David Woodhouse's 
> bk-commits mailer scripts could probably easily be tweaked to -not- set 
> an explicit Date header on the outgoing emails.
> 
> It then becomes a matter of deciding whether this is a good idea or not :)

The original changeset date is also in the body of the mail anyway so it
wouldn't be lost if we changed this. I have no real preference either
way. Bear in mind that the Date: header you got would then be the time
my script ran, not the time it was actually committed. That may differ
by days, in some cases (thankfully not often).

-- 
dwmw2


  reply	other threads:[~2005-03-10 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  2:41 bk commits and dates Benjamin Herrenschmidt
2005-03-10  3:28 ` Linus Torvalds
2005-03-10  5:49   ` Benjamin Herrenschmidt
2005-03-10 16:01     ` Linus Torvalds
2005-03-10  3:44 ` Michael Ellerman
2005-03-10  3:47 ` David S. Miller
2005-03-10  5:50   ` Benjamin Herrenschmidt
2005-03-10  6:13     ` Jeff Garzik
2005-03-10 14:11       ` David Woodhouse [this message]
2005-03-10 18:18         ` Tom Rini
2005-03-10 19:12           ` Olaf Hering

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=1110463905.4026.11.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --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