From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Brandon Stafford <brandon@pingswept.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] Fix some punctuation, wording, and caps in manual
Date: Tue, 07 Jun 2011 22:55:45 +0100 [thread overview]
Message-ID: <1307483745.15712.80.camel@rex> (raw)
In-Reply-To: <BANLkTi=RWRFGQ1ujgCY8Gk8jhr62HMo_vw@mail.gmail.com>
Hi Brandon,
On Fri, 2011-06-03 at 12:14 -0400, Brandon Stafford wrote:
> This patch contains what I hope are non-controversial improvements to
> the manual. Most of the changes are single characters, but the
> line-by-line diff makes the patch look large.
>
> This is my first patch to Bitbake, so please don't kill me
> immediately. (I originally sent this message, minus this sentence,
> around 2011-03-10, but the bitbake-dev list appeared to be silently
> dropping messages from 2011-03-07 until 2011-03-24. I resent it again
> on 2011-03-27. I'm now sending it to the post-migration bitbake-devel
> list on 2011-06-03.)
>
> Signed-off-by: Brandon Stafford <brandon@pingswept.org>
I tried to get this to apply but the patch appears corrupt and I can't
convince the patch tools to accept it. It looks like you sent html email
and that your mailer line wrapped the text in some way too.
Perhaps you could resend the patch as an attachment to the email or
alternatively don't send html emails and try and address the line
wrapping problem.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-07 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikY20mQoKfNaY6xsokcVabDnnaQKrvAmumBvv77@mail.gmail.com>
2011-06-03 16:14 ` [PATCH 1/1] Fix some punctuation, wording, and caps in manual Brandon Stafford
2011-06-07 21:55 ` Richard Purdie [this message]
2011-06-07 23:07 ` Brandon Stafford
2011-06-22 13:38 ` Paul Eggleton
2011-06-22 15:31 ` Richard Purdie
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=1307483745.15712.80.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=brandon@pingswept.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.