mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Evans" <mjevans1983@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: "Michael J. Evans" <mjevans1983@comcast.net>,
	"Neil Brown" <neilb@suse.de>, "Ingo Molnar" <mingo@redhat.com>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch v3 1/1] md: Software Raid autodetect dev list not array
Date: Tue, 28 Aug 2007 06:08:45 -0700	[thread overview]
Message-ID: <4877c76c0708280608m529296edgd83f9c08e3918815@mail.gmail.com> (raw)
In-Reply-To: <46D3A8AD.6000701@oracle.com>

On 8/27/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Michael J. Evans wrote:
> > On Monday 27 August 2007, Randy Dunlap wrote:
> >> On Mon, 27 Aug 2007 15:16:21 -0700 Michael J. Evans wrote:
> >>
> >>> =============================================================
> >>> --- linux/drivers/md/md.c.orig      2007-08-21 03:19:42.511576248 -0700
> >>> +++ linux/drivers/md/md.c   2007-08-21 04:30:09.775525710 -0700
> >>> @@ -24,4 +24,6 @@
> >>>
> >>> +   - autodetect dev list not array: Michael J. Evans
> > <mjevans1983@gmail.com>
> >>> +
> >> Nowadays we use an SCM for such comments, not the source file(s).
> >
> > SCM?  Is this automatic, where do I go to see it?
>
> See Documentation/SubmittingPatches:
> 14) The canonical patch format:
>
> The canonical patch message body contains the following:
>
>   - A "from" line specifying the patch author.
>
>   - An empty line.
>
>   - The body of the explanation, which will be copied to the
>     permanent changelog to describe this patch.
>
>   - The "Signed-off-by:" lines, described above, which will
>     also go in the changelog.
>
>   - A marker line containing simply "---".
>
>   - Any additional comments not suitable for the changelog.
>
>   - The actual patch (diff output).
>
>
> so just put whatever you want to be in the permanent SCM logs
> into the "body of the explanation" part of the email.
>
>
> --
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>

Oh, I see.  I forgot about the changelogs.  I'd send out version 5
now, but I'm not sure what kernel version to make the patch against.
2.6.23-rc4 is on kernel.org and I don't see any git snapshots.
Additionally I never could tell what git tree was the 'mainline' as it
isn't labeled with such a keyword (at least in the list of git trees I
saw).

  reply	other threads:[~2007-08-28 13:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200708222058.45480.mjevans1983@comcast.net>
2007-08-24  3:37 ` [patch " Neil Brown
2007-08-24  5:50   ` Michael Evans
2007-08-26 11:51   ` [patch v2 " Michael J. Evans
2007-08-26 12:20     ` Michael Evans
2007-08-27  3:41       ` Kyle Moffett
2007-08-27  7:56         ` Michael Evans
2007-08-26 12:56     ` Jan Engelhardt
2007-08-26 15:58       ` Michael Evans
2007-08-26 16:56     ` Randy Dunlap
2007-08-26 19:18       ` Michael Evans
2007-08-27 22:16         ` [patch v3 " Michael J. Evans
2007-08-27 22:30           ` Randy Dunlap
2007-08-28  4:38             ` Michael J. Evans
2007-08-28  4:46               ` Randy Dunlap
2007-08-28 13:08                 ` Michael Evans [this message]
2007-08-28 13:14                   ` Jan Engelhardt
2007-08-28 13:26                     ` Michael J. Evans
2007-08-28 13:24                   ` Bill Davidsen
2007-08-28 13:32                     ` Michael Evans
2007-08-28 16:15                       ` Randy Dunlap
2007-08-28 17:10                         ` Michael Evans
2007-08-28 17:22                           ` Randy Dunlap
2007-08-28 19:11                             ` Michael Evans
2007-08-28 19:16                               ` Randy Dunlap
2007-08-29  8:06                                 ` [patch v5 " Michael J. Evans
2007-08-29 15:18                                   ` Randy Dunlap
2007-08-28 13:27                 ` Michael J. Evans
2007-08-28  4:39             ` [patch v4 " Michael J. Evans

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=4877c76c0708280608m529296edgd83f9c08e3918815@mail.gmail.com \
    --to=mjevans1983@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mjevans1983@comcast.net \
    --cc=neilb@suse.de \
    --cc=randy.dunlap@oracle.com \
    /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®