From: Paul Jackson <pj@sgi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Documentation/patch-tags, one more time
Date: Fri, 8 Feb 2008 13:01:26 -0600 [thread overview]
Message-ID: <20080208130126.e05be25d.pj@sgi.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802080959130.2896@woody.linux-foundation.org>
Linus wrote:
> "From:" is not a tag. It's a special marker at the *top* (and _only_ the top)
So ... instead of listing "From:" as just another tag, I'd think it would
work if this one was listed in a separate section, perhaps at the end of this
Documentation/patch-tags document, such as:
From: In addition to the above tags, one can also specify the original author
of the change, who will end up as the commit author, with a special marker
at the top (very first line) of the patch, with a "From:" line. See further
Documentation/SubmittingPatches for usage of this "From:" line.
Question -- should this documentation of patch-tags be in its own file,
or added to Documentation/SubmittingPatches. If it remains in its own
file, then perhaps Documentation/SubmittingPatches should have a reference
to Documentation/patch-tags added.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-02-08 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:51 [PATCH] Documentation/patch-tags, one more time Jonathan Corbet
2008-02-08 17:07 ` Pekka Enberg
2008-02-08 18:00 ` Linus Torvalds
2008-02-08 19:01 ` Paul Jackson [this message]
2008-02-08 20:42 ` [PATCH] Documenting patch tags yet " Jonathan Corbet
2008-02-09 0:23 ` Paul Jackson
2008-02-09 8:37 ` Stefan Richter
2008-02-08 20:50 ` [PATCH] Documentation/patch-tags, " Junio C Hamano
2008-02-18 2:58 ` Neil Brown
2008-02-18 3:15 ` Paul Jackson
2008-02-18 3:58 ` Neil Brown
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=20080208130126.e05be25d.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.