All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Sona Sarmadi <sona.sarmadi@enea.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: Fix for CVE-2014-3566
Date: Wed, 5 Nov 2014 14:05:36 +0100	[thread overview]
Message-ID: <20141105130536.GA2457@jama> (raw)
In-Reply-To: <3230301C09DEF9499B442BBE162C5E482577C41F@SESTOEX04.enea.se>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

On Wed, Nov 05, 2014 at 12:31:56PM +0000, Sona Sarmadi wrote:
> Hi Paul,
> 
> 
> > Just to be clear, this is for the dora branch right?
> > 
> > Cheers,
> > Paul
> 
> Yes, I send the patch as below, why does not the branch name come in the subject :( ? 
> 
> git send-email --to=openembedded-core@lists.openembedded.org --confirm=always  --subject-prefix="dora][PATCH" 000*

Because you're sending already generated files (000*), it works only
when you specify git revisions (e.g. -1 my_branch).

Or you need to pass --subject-prefix when you're calling git
format-patch to generate them.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-11-05 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 12:23 [PATCH] openssl: Fix for CVE-2014-3566 Sona Sarmadi
2014-11-05 12:28 ` Burton, Ross
2014-11-05 12:28 ` Paul Eggleton
2014-11-05 12:31   ` Sona Sarmadi
2014-11-05 13:05     ` Martin Jansa [this message]
2014-11-05 13:58       ` Sona Sarmadi

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=20141105130536.GA2457@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=sona.sarmadi@enea.com \
    /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.