From: Michal Marek <mmarek@suse.cz>
To: Harald Dunkel <harri@afaics.de>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts/package/builddeb: include generated header files
Date: Mon, 28 May 2012 11:23:29 +0200 [thread overview]
Message-ID: <4FC34411.1070807@suse.cz> (raw)
In-Reply-To: <4FC15323.1070206@afaics.de>
On 27.5.2012 00:03, Harald Dunkel wrote:
>> You make easier for the receiving party if you send patches using
>> git send-email. And lkml should be always CCed in addition to the
>> maintainer and/or subsystem mailing list. Otherwise, the patch
>> itself was OK.
>>
>
> I tried to follow the doc on kernelnewbies, but I haven't seen the
> git command line. It would help very much if you could send me a
> pointer to some more up-to-date information, if you have it at hand.
The commandline is
git send-email --to=... --cc=... --cc=... ... <base>
or
git send-email --to=... --cc=... --cc=... ... <base>..<end>
<base> is the commit you based your changes on. So you usually do
git checkout -b my-fix master
<hack hack hack>
git send-email ... master..my-fix
Then the receiver can simply pipe the email(s) to 'git am' to apply the
changes. Of course git send-email is not mandatory, but if you use it,
you can be sure that the patch will be applicable without further
processing.
Michal
next prev parent reply other threads:[~2012-05-28 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 15:11 [PATCH] scripts/package/builddeb: include generated header files Harald Dunkel
2012-05-26 21:00 ` Michal Marek
2012-05-26 22:03 ` Harald Dunkel
2012-05-28 9:23 ` Michal Marek [this message]
2012-06-07 4:07 ` Harald Dunkel
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=4FC34411.1070807@suse.cz \
--to=mmarek@suse.cz \
--cc=harri@afaics.de \
--cc=linux-kbuild@vger.kernel.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.