From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Juliusz Chroboczek <jch@pps.jussieu.fr>,
git@vger.kernel.org
Subject: Re: git-format-patch should include a checksum
Date: Tue, 26 Jan 2010 16:45:07 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001261639550.17519@localhost.localdomain> (raw)
In-Reply-To: <fabb9a1e1001261526tc86c04em4c6ede23e109e66@mail.gmail.com>
On Wed, 27 Jan 2010, Sverre Rabbelier wrote:
>
> I would imagine that the checksum is taken over just the actual commit
> message, perhaps author information, and use the patch-id for the
> patch itself, that way any comments after triple dash would be ignored, right?
That wouldn't work either. People can, should, and do add extra things to
the message before applying it.
Examples of things I tend to add/change in the commit message:
- add ack's from people in the same thread
- add "Cc: stable@kernel.org"
- re-flow paragraphs when somebody uses a mailer that makes a mess of it.
- occasionally fix spelling and grammar
so if there is some checksum that screws that up and requires me to then
use a "--force" flag to apply it, that would be a bad thing.
I also do edit patches manually too. Having lived with people sending me
patches for the last almost twenty years, I can edit patches in my sleep.
Doing things like renaming new variables etc by search-and-replace on the
patch may not be something I do _often_, but it happens.
In short, it might make sense to have some anti-corruption logic, but I
suspect it needs a lot of thought.
Linus
next prev parent reply other threads:[~2010-01-27 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 22:34 git-format-patch should include a checksum Juliusz Chroboczek
2010-01-26 23:15 ` Sverre Rabbelier
2010-01-26 23:21 ` Junio C Hamano
2010-01-26 23:26 ` Sverre Rabbelier
2010-01-27 0:45 ` Linus Torvalds [this message]
2010-01-27 0:50 ` Sverre Rabbelier
2010-01-27 1:13 ` Nicolas Pitre
2010-01-27 1:25 ` Junio C Hamano
2010-01-27 1:25 ` Juliusz Chroboczek
2010-01-27 1:35 ` Junio C Hamano
2010-01-27 3:01 ` 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=alpine.LFD.2.00.1001261639550.17519@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jch@pps.jussieu.fr \
--cc=srabbelier@gmail.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