Git development
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Brian Gernhardt <benabik@silverinsanity.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Commit message for 1240f94 has mail headers
Date: Sun, 6 Jul 2008 23:19:07 +0200	[thread overview]
Message-ID: <20080706211907.GL4729@genesis.frugalware.org> (raw)
In-Reply-To: <2C6B8E28-3E8A-414E-9DB7-626E9709C831@silverinsanity.com>

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

On Sun, Jul 06, 2008 at 04:00:23AM -0400, Brian Gernhardt <benabik@silverinsanity.com> wrote:
> I don't think all those mail headers are supposed to be in there.  I don't 
> know if it's too late to fix that, but I thought you should know.

My fault, I noticed it but I forgot to send a reminder about it before
it hit next.

Sorry.

(I suppose it won't be fixed, unless merge-in-c won't hit master before
1.6.0, which is hopefully unlikely. ;-) )

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-07-06 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06  8:00 Commit message for 1240f94 has mail headers Brian Gernhardt
2008-07-06 21:19 ` Miklos Vajna [this message]

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=20080706211907.GL4729@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=benabik@silverinsanity.com \
    --cc=git@vger.kernel.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