From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Joey Hess <joey@kitenet.net>,
git@vger.kernel.org
Subject: Re: git notes: notes
Date: Sun, 24 Jan 2010 15:20:09 +0100 [thread overview]
Message-ID: <vpq7hr7zism.fsf@bauges.imag.fr> (raw)
In-Reply-To: <7veilk1o3s.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 20 Jan 2010 13\:08\:07 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>> No, but outputting the note as part of the log is the standard. So for
>> example, when you do a format-patch | apply cycle, format-patch will
>> insert the note as part of the commit message, and apply will *store*
>> the note text (including Note:\n) as part of the commit message of the
>> new commit.
>
> Thanks; that was the kind of breakage report I was looking for (and wished
> to have heard a lot earlier). Personally I find it is unexcusable that
> format-patch defaults to giving notes.
OTOH, format-patch could give the notes, below the ---, where it will
be ignored by apply. That would make notes handy to prepare a patch
serie with additional messages: prepare everything within Git, and use
git send-email to send it.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-01-24 14:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 5:03 git notes: notes Joey Hess
2010-01-20 9:48 ` Thomas Rast
2010-01-20 18:14 ` Joey Hess
2010-01-20 10:48 ` Johan Herland
2010-01-20 18:24 ` Joey Hess
2010-01-20 19:30 ` Junio C Hamano
2010-01-20 19:56 ` Joey Hess
2010-01-20 20:10 ` Junio C Hamano
2010-01-20 20:36 ` Joey Hess
2010-01-20 20:54 ` Jeff King
2010-01-20 20:59 ` Junio C Hamano
2010-01-20 21:31 ` Jeff King
2010-01-20 21:41 ` Jeff King
2010-01-20 22:07 ` Junio C Hamano
2010-01-20 22:21 ` Jeff King
2010-01-20 21:02 ` Michael J Gruber
2010-01-20 21:08 ` Junio C Hamano
2010-01-20 21:36 ` Jeff King
2010-01-20 21:59 ` Junio C Hamano
2010-01-20 22:25 ` Jeff King
2010-01-20 22:33 ` Junio C Hamano
2010-01-20 22:58 ` Johannes Schindelin
2010-01-20 23:06 ` Jeff King
2010-01-20 23:14 ` Junio C Hamano
2010-01-21 2:54 ` Johan Herland
2010-01-21 3:03 ` Junio C Hamano
2010-01-21 3:37 ` Junio C Hamano
2010-01-21 8:45 ` Michael J Gruber
2010-01-24 14:20 ` Matthieu Moy [this message]
2010-01-24 14:27 ` Sverre Rabbelier
2010-01-21 2:05 ` Johan Herland
2010-01-21 3:59 ` Johannes Schindelin
2010-01-21 4:05 ` Joey Hess
2010-01-27 11:55 ` Johan Herland
2010-01-25 18:08 ` John Koleszar
2010-01-27 20:01 ` Christian Couder
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=vpq7hr7zism.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
/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).