From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: If you want me to quit I will quit
Date: Sun, 27 Apr 2008 16:28:18 +0200 [thread overview]
Message-ID: <48148D82.3050204@s5r6.in-berlin.de> (raw)
In-Reply-To: <1209298055.1475.0.camel@dax.rpnet.com>
Richard Purdie wrote:
> Its worth realising that these fix patches contain useful information
> too, e.g. they might be by different authors and its also interesting in
> some senses to see what fixes were applied to the original patch, why
> etc. since it is history and that is what the SCM effectively stores.
Important things can be noted in the patch description. We can also
refer to mailinglist archives and bug trackers in the patch description.
Caveats: Changing the patch description means changing the patch
identity (which different SCMs treat with different rigor). Also, a
number of SCM tools assume that there is exactly one author of a patch.
(Workaround: Track coauthors informally in the patch description.)
...
> On the other hand I agree that the patches in -mm often have stupid
> typos etc which aren't interesting in the history but where do you draw
> the line?
Indeed. It's the question of when do I release what to whom.
--
Stefan Richter
-=====-==--- -=-- ==-==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-04-27 14:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 6:14 [BUILDFIX PATCH] au0828: debug is a poor global identifier Harvey Harrison
2008-04-26 11:00 ` If you want me to quit I will quit Adrian Bunk
2008-04-26 11:27 ` Sam Ravnborg
2008-04-26 14:44 ` Adrian Bunk
2008-04-26 16:51 ` Linus Torvalds
2008-04-26 17:09 ` Adrian Bunk
2008-04-26 17:21 ` Linus Torvalds
2008-04-26 17:35 ` Adrian Bunk
2008-04-26 17:56 ` Linus Torvalds
2008-04-26 14:51 ` Andrew Morton
2008-04-26 15:23 ` Adrian Bunk
2008-04-26 15:44 ` Andrew Morton
2008-04-26 17:16 ` Adrian Bunk
2008-04-26 17:20 ` Andrew Morton
2008-04-26 17:27 ` Adrian Bunk
2008-04-26 17:35 ` Linus Torvalds
2008-04-26 17:31 ` Linus Torvalds
2008-04-26 17:42 ` Sam Ravnborg
2008-04-26 18:26 ` Linus Torvalds
2008-04-26 18:51 ` Stefan Richter
2008-04-26 19:05 ` Linus Torvalds
2008-04-26 19:18 ` Linus Torvalds
2008-04-26 20:30 ` Andrew Morton
2008-04-26 20:35 ` Linus Torvalds
2008-04-28 19:05 ` Romano Giannetti
2008-04-26 20:49 ` Stefan Richter
2008-04-27 12:07 ` Richard Purdie
2008-04-27 14:28 ` Stefan Richter [this message]
2008-04-26 19:43 ` Stefan Richter
2008-04-27 0:31 ` David Miller
2008-04-27 2:58 ` Jeff Garzik
2008-04-27 16:09 ` Ingo Molnar
2008-04-26 16:21 ` Bartlomiej Zolnierkiewicz
2008-04-26 17:10 ` Adrian Bunk
2008-04-26 19:20 ` Harvey Harrison
2008-04-26 19:42 ` Adrian Bunk
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=48148D82.3050204@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rpurdie@rpsys.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®