From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 11/11] Support bundles in builtin-clone
Date: Sun, 9 Mar 2008 21:56:54 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.1.00.0803092155450.3975@racer.site> (raw)
In-Reply-To: <alpine.LNX.1.00.0803091447230.19665@iabervon.org>
Hi,
On Sun, 9 Mar 2008, Daniel Barkalow wrote:
> On Sun, 9 Mar 2008, Johannes Schindelin wrote:
>
> > On Sat, 8 Mar 2008, Johannes Schindelin wrote:
> >
> > > This forward-ports c6fef0bb(clone: support cloning full bundles) to
> > > the builtin clone.
> > >
> > > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> > > ---
> >
> > Wow... Is this a new send-email feature? I did not send this email...
>
> Nope, it's an old format-patch feature. format-patch generates the
> messages with the From: being the commit author, and my MTA doesn't
> complain about the fact that I'm sending email with some entirely
> different From:. It would probably be more clever to have format-patch
> use the committer or the current user as the From:, and put an
> additional From: in the message body with the author if it's not the
> email From:.
I think that makes sense.
> Of course, you did sort of send that email
> (http://permalink.gmane.org/gmane.comp.version-control.git/75743).
Sort of.
Of course, I am okay with it, but I consider the From: issue a real bug in
send-email (or format-patch, if you want).
Ciao,
Dscho
next prev parent reply other threads:[~2008-03-09 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 23:04 [PATCH 11/11] Support bundles in builtin-clone Johannes Schindelin
2008-03-08 23:28 ` Johannes Schindelin
2008-03-09 19:00 ` Daniel Barkalow
2008-03-09 20:56 ` Johannes Schindelin [this message]
2008-03-09 21:59 ` Daniel Barkalow
2008-03-10 5:55 ` Junio C Hamano
2008-03-10 6:32 ` Junio C Hamano
2008-03-10 10:56 ` Johannes Schindelin
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=alpine.LSU.1.00.0803092155450.3975@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).