Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Apelete Seketeli <apelete@seketeli.net>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] opkg-utils: Update SRC_URI to git.yoctoproject.org
Date: Wed, 9 May 2012 23:52:38 +0200	[thread overview]
Message-ID: <20120509215237.GR3781@hermes> (raw)
In-Reply-To: <20120509210020.GI12898@jama.jama.net>

Le 09-May-12, Martin Jansa a écrit:
> On Wed, May 09, 2012 at 09:16:56PM +0200, Apelete Seketeli wrote:
> > Hi,
> > 
> > Le 02-May-12, Apelete Seketeli a écrit:
> > > 
> > > Okay, I finally got some time to works on this.
> > > I asked on the yocto ML to get the original patches applied, and they
> > > actually got applied (thanks to Richard Purdie).
> > > 
> > > Please find attached the patch to get the changes into oe-classic. I
> > > don't know if I should create a new thread to submit it, I would
> > > gladly do so if asked to.
> > 
> > The patch has just been applied in oe-classic, thanks to Kristoffer
> > Ericson.
> > 
> > http://cgit.openembedded.org/openembedded/commit/?id=1ff63aa26e3088ba2d30e491d74a31caf25c3d83
> > 
> > I am new to the list, so I am not used to the process, but would you
> > please tell me what the rule for the author and committer field is ?
> > I would have naively expect to see my name there.
> 
> You did it almost right and Kristoffer's name should be only in committer 
> field and yours in author.
> 
> Next time when sending new version use PATCHv2 prefix and don't send
> your patch in reply as inline. If you download mbox version from
> patchwork
> http://patchwork.openembedded.org/patch/26863/
> you'll see that e.g. my reply to you get's included in commit message of
> such patch which doesn't belong there and committer needs to use 
> git commit --amend  -s
> to strip unwanted text..

Thanks for the detailed explanation. I get your point, I will follow
these instructions next time and submit the patch as a separate mail
in a thread.

Cheers.
-- 
        Apelete



  reply	other threads:[~2012-05-09 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 21:46 [PATCH] opkg-utils: Update SRC_URI to git.yoctoproject.org Apelete Seketeli
2012-04-11 12:55 ` Martin Jansa
2012-04-12 20:44   ` Apelete Seketeli
2012-04-12 21:01     ` Martin Jansa
2012-05-02 21:00       ` Apelete Seketeli
2012-05-09 19:16         ` Apelete Seketeli
2012-05-09 21:00           ` Martin Jansa
2012-05-09 21:52             ` Apelete Seketeli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-11 21:39 Apelete Seketeli

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=20120509215237.GR3781@hermes \
    --to=apelete@seketeli.net \
    --cc=kristoffer.ericson@gmail.com \
    --cc=martin.jansa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox