git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* format-patch usage
@ 2008-01-14  0:40 William Morgan
  2008-01-14  1:02 ` Junio C Hamano
  0 siblings, 1 reply; 2+ messages in thread
From: William Morgan @ 2008-01-14  0:40 UTC (permalink / raw)
  To: Git Mailing List

Hi all,

Two questions from a git neophyte about using format-patch:

First, what's the point of adding the Signed-off-by footer, if you're
the author of the patch? I can see the utility of the committer adding
this, as a record of who committed it, but if you wrote a patch and are
submitting it to the list, then you've presumably "signed off", haven't
you? Or is there some subtle distinction between exploratory patches and
"real" patches being made?

Second, it seems like commentary about a patch can be placed after the
"---" but before the "diff --git" lines. Is that correct? Is that
accepted practice? It seems a little backwards to have the commit
message first, then the commentary. Am I correct in assuming that
git-apply ignores anything between those two lines, including the diff
stat, and so that's the reason people put it there?

Thanks,

-- 
William <wmorgan-git@masanjin.net>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: format-patch usage
  2008-01-14  0:40 format-patch usage William Morgan
@ 2008-01-14  1:02 ` Junio C Hamano
  0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2008-01-14  1:02 UTC (permalink / raw)
  To: William Morgan; +Cc: Git Mailing List

William Morgan <wmorgan-git@masanjin.net> writes:

> Two questions from a git neophyte about using format-patch:

Both come from the established kernel Documentation/SubmittingPatches
convention.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-01-14  1:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-14  0:40 format-patch usage William Morgan
2008-01-14  1:02 ` Junio C Hamano

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).