From: "Eric Bénard" <eric@eukrea.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] how to create patches for mailing
Date: Thu, 24 Jan 2013 09:40:33 +0100 [thread overview]
Message-ID: <20130124094033.6a99ddea@e6520eb> (raw)
In-Reply-To: <CAP3+TEq519PPHFhu2wYxv6B82Xkou5Q7Ct8OzH9s-jCcoVjWmQ@mail.gmail.com>
Hi Maxim,
Le Thu, 24 Jan 2013 12:21:30 +0400,
Maxim Podbereznyy <lisarden@gmail.com> a ?crit :
> Your instructions are exceptional! However I have a few questions:
> 1) why should I generate patches for 1st 3 patch, because I have only one?
> 2) if there are 3 patches (only 1 is mine) + a cover which exactly
> <required-patches> should I send?
>
you have more details here :
http://www.denx.de/wiki/U-Boot/Patches
Eric
prev parent reply other threads:[~2013-01-24 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 7:40 [U-Boot] how to create patches for mailing Maxim Podbereznyy
2013-01-24 8:02 ` Hebbar, Gururaja
2013-01-24 8:21 ` Maxim Podbereznyy
2013-01-24 8:25 ` Hebbar, Gururaja
2013-01-24 8:40 ` Eric Bénard [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=20130124094033.6a99ddea@e6520eb \
--to=eric@eukrea.com \
--cc=u-boot@lists.denx.de \
/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.