From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [Question] How to make a patch?
Date: Sat, 10 Aug 2013 01:07:22 +0100 [thread overview]
Message-ID: <20130810000722.GD4493@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <52057F7F.7090406@gmail.com>
On Sat, Aug 10, 2013 at 08:47:11AM +0900, Akira Hayakawa wrote:
> Do you mean
> making a patch against rc4 in linux-next is not preferred?
The risk of patching against linux-next directly is that you might find
yourself debugging problems in other subsystems when you try to test:)
But others would say that is that an advantage:)
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.
(For example, I think I saw someone point out that the interface needs a
careful review and might work better if done a different way.)
Alasdair
next prev parent reply other threads:[~2013-08-10 0:07 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 [this message]
2013-08-10 0:43 ` Akira Hayakawa
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=20130810000722.GD4493@agk-dp.fab.redhat.com \
--to=agk@redhat.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 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.