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

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

I can't apply this patch. It goes beyond the doc files so I need to leave it to Richard to apply.

Scott

On Mon, May 19, 2014 at 1:34 AM, Rifenbark, Scott M
<scott.m.rifenbark@...> 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@... [mailto:yocto-
bounces@...] On Behalf Of Chris Morgan
Sent: Sunday, May 18, 2014 11:29 AM
To: yocto@...
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?

Chris

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@...> 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@... [mailto:yocto-
bounces@...] On Behalf Of Chris Morgan
Sent: Sunday, May 18, 2014 11:29 AM
To: yocto@...
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