dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Akira Hayakawa <ruby.wktk@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [Question] How to make a patch?
Date: Sat, 10 Aug 2013 09:43:27 +0900	[thread overview]
Message-ID: <52058CAF.6010802@gmail.com> (raw)
In-Reply-To: <20130810000722.GD4493@agk-dp.fab.redhat.com>

On 8/10/13 9:07 AM, Alasdair G Kergon wrote:
> It really shouldn't matter which point you choose at the moment because 
> very little (nothing?) of relevance to your patch should be changing and
> there will still be more revisions before the code is ready.

Thanks, I understand.

I will write code on linux-dm and
make my patch on v3.11-rc3.

Akira

      reply	other threads:[~2013-08-10  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 23:12 [Question] How to make a patch? Akira Hayakawa
2013-08-09 23:22 ` Alasdair G Kergon
2013-08-09 23:47   ` Akira Hayakawa
2013-08-10  0:07     ` Alasdair G Kergon
2013-08-10  0:43       ` Akira Hayakawa [this message]

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=52058CAF.6010802@gmail.com \
    --to=ruby.wktk@gmail.com \
    --cc=dm-devel@redhat.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;
as well as URLs for NNTP newsgroup(s).