From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 2/2] README: add -s to git send-email example
Date: Thu, 26 Jan 2017 17:03:18 -0800 [thread overview]
Message-ID: <5dfb289d-2a44-1233-3761-f7e372c6dafc@gmail.com> (raw)
In-Reply-To: <CAEHkU3UX4NhOVvg6QXcuWgw_H5Z1EaOgih3Lsj9D+hfvC1s44A@mail.gmail.com>
what happens if commits are already having a sign-off ?
On 1/26/17 2:27 PM, Max Krummenacher wrote:
> ping
>
> Any comments on this one?
>
> Max
>
> 2017-01-17 0:09 GMT+01:00 Max Krummenacher <max.oss.09@gmail.com>:
>> Prevent missing Signed-off-by lines.
>>
>> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
>> ---
>> README | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/README b/README
>> index 647404b..effe2f9 100644
>> --- a/README
>> +++ b/README
>> @@ -26,7 +26,7 @@ Maintainers: Eric Bénard <eric@eukrea.com>
>> Otavio Salvador <otavio@ossystems.com.br>
>>
>> When sending single patches, please use something like :
>> -git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-browser][PATCH'
>> +git send-email -1 -s --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-browser][PATCH'
>>
>> TODO
>> ----
>> --
>> 2.6.6
>>
next prev parent reply other threads:[~2017-01-27 1:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 23:09 [meta-browser][PATCH 1/2] firefox: remove nss private libs setting Max Krummenacher
2017-01-16 23:09 ` [meta-browser][PATCH 2/2] README: add -s to git send-email example Max Krummenacher
2017-01-26 22:27 ` Max Krummenacher
2017-01-27 1:03 ` Khem Raj [this message]
2017-01-27 10:10 ` Otavio Salvador
2017-01-27 10:28 ` Anders Darander
2017-01-27 11:15 ` Max Krummenacher
2017-01-27 11:55 ` Otavio Salvador
2017-01-27 17:40 ` Khem Raj
2017-01-26 22:27 ` [meta-browser][PATCH 1/2] firefox: remove nss private libs setting Max Krummenacher
2017-01-27 1:02 ` Khem Raj
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=5dfb289d-2a44-1233-3761-f7e372c6dafc@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.