From: Steve James <ste@junkomatic.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] leveldb: new package
Date: Wed, 24 Dec 2014 10:54:15 +0000 [thread overview]
Message-ID: <201412241054.16028.ste@junkomatic.net> (raw)
In-Reply-To: <20141223205124.0d05b9dc@free-electrons.com>
On Tuesday 23 Dec 2014 19:51:24 Thomas Petazzoni wrote:
> Dear Steve James,
>
--snip--
>
> Thanks for this new version. However, your patch has been line-wrapped
> by your e-mail client. Could you try to send it with 'git send-email'
> instead? See the Buildroot instructions for some details about this.
Oh dear, that's embarassing. This has happened because I am at home using a
different client. Yes, I should have used send-email. Sorry to waste your
time Thomas. Fresh patch follows...
prev parent reply other threads:[~2014-12-24 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 17:16 [Buildroot] [PATCH v2] leveldb: new package Steve James
2014-12-23 19:51 ` Thomas Petazzoni
2014-12-24 10:54 ` Steve James [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=201412241054.16028.ste@junkomatic.net \
--to=ste@junkomatic.net \
--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 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.