From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Morgan <chmorgan@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH] Documentation improvements for gitsm:// fetcher
Date: Mon, 19 May 2014 12:07:43 +0100 [thread overview]
Message-ID: <1400497663.28353.164.camel@ted> (raw)
In-Reply-To: <CAAPegz0j21Jc19ze3BDcDcNt0iE3hQEGF0Y1eJdv8epZqR3SzA@mail.gmail.com>
On Mon, 2014-05-19 at 06:42 -0400, Chris Morgan wrote:
> On Mon, May 19, 2014 at 1:34 AM, Rifenbark, Scott M
> <scott.m.rifenbark@intel.com> wrote:
> > Hi,
> >
> > This patch is not coming across to me intact. The process I use for patches is to take the attachment from my Thunderbird account and save it as an .EML file. Then, I mail that .EML file to my Linux box gmail account. From there I process the patch using the 'patch' command as normal. For some reason, the .EML file when it arrives to my gmail account has long lines of random characters (gibberish) that the patch program is unable to deal with. I am unsure if it is a problem on my end with my process or with the patch generation.
> >
> > Scott
> >
> >>-----Original Message-----
> >>From: yocto-bounces@yoctoproject.org [mailto:yocto-
> >>bounces@yoctoproject.org] On Behalf Of Chris Morgan
> >>Sent: Sunday, May 18, 2014 11:29 AM
> >>To: yocto@yoctoproject.org
> >>Subject: [yocto] [PATCH] Documentation improvements for gitsm:// fetcher
> >>
> >>Rough patch for documentation improvements now that I know how gitsm
> >>should work and to help others that might be caught by switching from git://
> >>to gitsm:// URIs.
> >>
> >>Chris
>
>
> I'm not sure what might be doing on. I'm adding it to the email
> directly from the gmail web interface from the file created via 'git
> format-patch -1'. I looked but don't see any email settings around
> mime in gmail's settings. Should I not be sending via email? Am I
> missing a setting?
Things were a little confusing for Scott since the patch is against
poky, not the bitbake repository. I've merged in the patch, thanks.
In future please include a Signed-off-by line and with the shortlog in
the commit message, format it as per the contribution guidelines so that
someone can easily see which code it affects (fetch2/gitsm: is
appropriate in this case).
Cheers,
Richard
prev parent reply other threads:[~2014-05-19 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 18:28 [PATCH] Documentation improvements for gitsm:// fetcher Chris Morgan
2014-05-19 5:34 ` Rifenbark, Scott M
2014-05-19 6:03 ` Rifenbark, Scott M
2014-05-19 10:42 ` Chris Morgan
2014-05-19 11:07 ` Richard Purdie [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=1400497663.28353.164.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=chmorgan@gmail.com \
--cc=yocto@yoctoproject.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.