All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFD] Explicitly documenting patch submission
Date: Mon, 24 May 2004 22:49:20 -0500	[thread overview]
Message-ID: <20040525034920.GY5414@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405241400280.32189@ppc970.osdl.org>

On Mon, May 24, 2004 at 02:05:40PM -0700, Linus Torvalds wrote:
> 
> 
> On Mon, 24 May 2004, Thomas Gleixner wrote:
> > 
> > What I'm missing in this discussion is a clear distinction between patches and 
> > contributions.
> 
> Well, I'm not sure such a clear distinction exists.

Actually, there is a question as to how to sign off on something that
eventually gets rolled into something larger? Simply collect all the
signatories? Andrew aggregates patches on a fairly regular basis. How
about stuff that gets merged from the CVS trees of public projects? I
think we need a way to say "this came from an aggregate external
source" for patches that aren't simply passed along one by one.
Perhaps something like:

Signed-off-by: J Random hacker <foo@bar.com> from http://baz.sourceforge.net

> Any process that doesn't allow for common sense is just broken, and
> clearly from a _legal_ standpoint it doesn't matter if we track who fixed
> out (atrocious) spelling errors.

"our"

-- 
Mathematics is the supreme nostalgia of our time.

  parent reply	other threads:[~2004-05-25  3:49 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1YUY7-6fF-11@gated-at.bofh.it>
2004-05-24 19:57 ` [RFD] Explicitly documenting patch submission Andi Kleen
2004-05-24 20:07   ` Davide Libenzi
2004-05-24 20:19     ` Joe Perches
2004-05-24 20:45     ` Linus Torvalds
2004-05-24 21:16       ` Davide Libenzi
2004-05-24 21:38         ` Linus Torvalds
2004-05-25  0:41       ` Francis J. A. Pinteric
2004-05-25  1:56         ` viro
2004-05-24 20:31   ` Linus Torvalds
2004-05-24 22:01     ` Andi Kleen
2004-05-24 22:14       ` Linus Torvalds
2004-05-24 20:50   ` Thomas Gleixner
2004-05-24 21:05     ` Linus Torvalds
2004-05-24 21:20       ` Thomas Gleixner
2004-06-10  8:00         ` Pavel Machek
2004-05-25  3:49       ` Matt Mackall [this message]
2004-05-25  4:02         ` Linus Torvalds
2004-05-25 11:11           ` Giuseppe Bilotta
2004-05-25 13:48             ` Steven Cole
2004-05-25 14:12             ` La Monte H.P. Yarroll
2004-05-24 21:19   ` Horst von Brand
     [not found] <A6974D8E5F98D511BB910002A50A6647615FD265@hdsmsx403.hd.intel.com>
2004-06-03  6:38 ` Len Brown
2004-05-27  6:20 Larry McVoy
2004-05-27  8:04 ` Andrew Morton
2004-05-27 14:51   ` Larry McVoy
2004-05-27 15:18     ` Jörn Engel
2004-05-27 16:13     ` Jon Smirl
2004-05-27 21:09   ` La Monte H.P. Yarroll
2004-05-27 21:46     ` Theodore Ts'o
2004-05-28 13:24       ` Larry McVoy
2004-05-28 15:07         ` Theodore Ts'o
2004-05-28 15:19           ` Dave Jones
2004-05-28 15:27             ` Larry McVoy
2004-05-28 15:35               ` Dave Jones
2004-05-28 17:11             ` Theodore Ts'o
2004-05-28 17:16               ` Larry McVoy
2004-05-28 15:24           ` Larry McVoy
     [not found] <20040525110000.27463.19462.Mailman@lists.us.dell.com>
2004-05-25 15:03 ` Justin Michael
     [not found] <1ZBgK-68x-3@gated-at.bofh.it>
2004-05-25  6:43 ` Kai Henningsen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24 23:05 Albert Cahalan
2004-05-25  3:50 ` Linus Torvalds
2004-05-25 19:28   ` Horst von Brand
2004-05-23 23:19 Shane Shrybman
2004-05-23  6:46 Linus Torvalds
2004-05-23  7:41 ` Neil Brown
2004-05-23  8:02 ` Arjan van de Ven
2004-05-23 15:25   ` Greg KH
2004-05-23 15:35     ` Arjan van de Ven
2004-05-23 15:42       ` Greg KH
2004-05-23 18:03       ` Matt Mackall
2004-05-23 15:38     ` Ian Stirling
2004-05-23 15:44       ` Greg KH
2004-05-23 16:01       ` Linus Torvalds
2004-05-23 15:53   ` Linus Torvalds
2004-05-23 16:33 ` Horst von Brand
2004-05-23 17:06   ` Linus Torvalds
2004-05-23 17:32     ` Roman Zippel
2004-05-23 17:55 ` Joe Perches
2004-05-23 19:00   ` Jeff Garzik
2004-05-23 19:12     ` Joe Perches
2004-05-23 21:41   ` Francois Romieu
2004-05-23 19:01 ` Davide Libenzi
2004-05-23 19:20   ` Linus Torvalds
2004-05-25 15:20     ` La Monte H.P. Yarroll
2004-05-25 21:16       ` H. Peter Anvin
2004-05-25  6:32 ` Daniel Phillips
2004-05-25 18:11   ` Paul Jackson
2004-05-25  7:06 ` Arjan van de Ven
2004-05-25 15:32   ` Steven Cole
2004-05-25 16:02     ` Bradley Hook
2004-05-25 18:51       ` La Monte H.P. Yarroll
2004-05-25 19:44         ` Bradley Hook
2004-05-26  4:16         ` Daniel Phillips
2004-05-25 13:11 ` Ben Collins
2004-05-25 17:15   ` Linus Torvalds
2004-05-25 17:18     ` Ben Collins
2004-05-25 18:02       ` Dave Jones
2004-05-25 18:06         ` Ben Collins
2004-05-25 18:51           ` Linus Torvalds
2004-05-25 15:00 ` raven
2004-05-25 15:44 ` La Monte H.P. Yarroll
2004-05-25 16:25   ` Linus Torvalds
2004-05-25 16:43     ` La Monte H.P. Yarroll
2004-05-25 17:40   ` Valdis.Kletnieks
2004-05-25 17:52     ` Linus Torvalds
2004-05-25 16:42 ` J. Bruce Fields
2004-05-25 17:05   ` Linus Torvalds
2004-05-25 18:08     ` Andy Isaacson
2004-05-25 20:10       ` Matt Mackall
2004-06-10 12:58         ` Pavel Machek

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=20040525034920.GY5414@waste.org \
    --to=mpm@selenic.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.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.