|
@@ -396,13 +396,13 @@ you are responsible for last-minute changes. Example :
|
|
[lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]
|
|
[lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]
|
|
Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
|
|
Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
|
|
|
|
|
|
-This practise is particularly helpful if you maintain a stable branch and
|
|
|
|
|
|
+This practice is particularly helpful if you maintain a stable branch and
|
|
want at the same time to credit the author, track changes, merge the fix,
|
|
want at the same time to credit the author, track changes, merge the fix,
|
|
and protect the submitter from complaints. Note that under no circumstances
|
|
and protect the submitter from complaints. Note that under no circumstances
|
|
can you change the author's identity (the From header), as it is the one
|
|
can you change the author's identity (the From header), as it is the one
|
|
which appears in the changelog.
|
|
which appears in the changelog.
|
|
|
|
|
|
-Special note to back-porters: It seems to be a common and useful practise
|
|
|
|
|
|
+Special note to back-porters: It seems to be a common and useful practice
|
|
to insert an indication of the origin of a patch at the top of the commit
|
|
to insert an indication of the origin of a patch at the top of the commit
|
|
message (just after the subject line) to facilitate tracking. For instance,
|
|
message (just after the subject line) to facilitate tracking. For instance,
|
|
here's what we see in 2.6-stable :
|
|
here's what we see in 2.6-stable :
|