From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add hash file
Date: Mon, 02 Feb 2015 09:03:19 -0600 [thread overview]
Message-ID: <54CF91B7.3070308@ou.edu> (raw)
In-Reply-To: <20150202105016.4b24eddf@free-electrons.com>
On 2/2/2015 3:50 AM, Thomas Petazzoni wrote:
> Dear Steve Kenton,
>
> On Mon, 2 Feb 2015 05:40:53 +0000, Steve Kenton wrote:
>> Signed-off-by: Steve Kenton<skenton@ou.edu>
>> ---
>> package/cdrtools/cdrtools.hash | 3 +++
>> 1 file changed, 3 insertions(+)
>> create mode 100644 package/cdrtools/cdrtools.hash
> This patch should not be separated from the previous, it should be
> merged with it.
This was my first attempt at git. I tried to follow the directions in
the buildroot manual but
since these were separate commits they generated separate emails using the
git format patch command example. What should it be to make it all one
patch?
Steve
next prev parent reply other threads:[~2015-02-02 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 5:40 [Buildroot] [PATCH 1/2] Cdrtools is a set of command line programs that allows to record CD/DVD/BluRay media. This package contains the cdrecord & mkisofs programs Steve Kenton
2015-02-02 5:40 ` [Buildroot] [PATCH 2/2] Add hash file Steve Kenton
2015-02-02 9:50 ` Thomas Petazzoni
2015-02-02 15:03 ` Steve Kenton [this message]
2015-02-02 16:55 ` Thomas Petazzoni
2015-02-02 9:35 ` [Buildroot] [PATCH 1/2] Cdrtools is a set of command line programs that allows to record CD/DVD/BluRay media. This package contains the cdrecord & mkisofs programs Thomas Petazzoni
2015-02-02 14:59 ` Steve Kenton
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=54CF91B7.3070308@ou.edu \
--to=skenton@ou.edu \
--cc=buildroot@busybox.net \
/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