All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe] [V2 PATCH 1/5] dash: use BP in SRC_URI
Date: Tue, 6 Jan 2015 08:07:26 +0800	[thread overview]
Message-ID: <54AB273E.4030600@windriver.com> (raw)
In-Reply-To: <20150105232609.GB19402@jama>



On 01/06/2015 07:26 AM, Martin Jansa wrote:
> On Tue, Jan 06, 2015 at 06:59:34AM +0800, Robert Yang wrote:
>>
>>
>> On 01/05/2015 07:59 PM, Martin Jansa wrote:
>>> Thanks for v2
>>>
>>> Please remember to update your old series as superseded when pushing
>>> newer version, it would help me a lot when sorting the pending patches.
>>
>> Hi Matin, what did you mean about: "update your old series as superseded",
>> please ? I can't understand this clearly.
>
> See
> http://www.openembedded.org/wiki/Patchwork
> and list of patches here
> http://patchwork.openembedded.org/project/oe/list/
>
> It helps me a lot when the submitters update status of their patches
> (because they usually don't have so many of them and they should know if
> they were applied, rejected in e-mail review or superseded when they
> send new version).
>
> My multi-layer triage usually starts by finding duplicate changes,
> marking all but latest as superseded, then adding them to right bundle
> if they belong to layer with separate maintainer and then cherry-pick
> the rest to master-next (or update it there).
>
> Any help in this triage helps me to do it faster and possibly more often
> (but even now I do it as often as I have jenkins server available for
> another round of testing)

Got it, thanks.

// Robert

>
>>
>> // Robert
>>
>>>
>>> On Sun, Jan 04, 2015 at 06:30:09PM -0800, Robert Yang wrote:
>>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>>> ---
>>>>    meta-oe/recipes-extended/dash/dash_0.5.8.bb |    2 +-
>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/meta-oe/recipes-extended/dash/dash_0.5.8.bb b/meta-oe/recipes-extended/dash/dash_0.5.8.bb
>>>> index c2b5249..4961d7b 100644
>>>> --- a/meta-oe/recipes-extended/dash/dash_0.5.8.bb
>>>> +++ b/meta-oe/recipes-extended/dash/dash_0.5.8.bb
>>>> @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b5262b4a1a1bff72b48e935531976d2e"
>>>>
>>>>    inherit autotools update-alternatives
>>>>
>>>> -SRC_URI = "http://gondor.apana.org.au/~herbert/dash/files/${PN}-${PV}.tar.gz"
>>>> +SRC_URI = "http://gondor.apana.org.au/~herbert/${BPN}/files/${BP}.tar.gz"
>>>>    SRC_URI[md5sum] = "5c152209680dab3c319e8923f6c51378"
>>>>    SRC_URI[sha256sum] = "c6db3a237747b02d20382a761397563d813b306c020ae28ce25a1c3915fac60f"
>>>>
>>>> --
>>>> 1.7.9.5
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>
>>>
>>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
>


  reply	other threads:[~2015-01-06  0:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  2:30 [meta-oe] [V2 PATCH 1/5] dash: use BP in SRC_URI Robert Yang
2015-01-05  2:30 ` [meta-oe] [V2 PATCH 2/5] rarpd: use BPN " Robert Yang
2015-01-05  2:30 ` [meta-oe] [V2 PATCH 3/5] procmail: " Robert Yang
2015-01-05  2:30 ` [meta-oe] [V2 PATCH 4/5] smem: " Robert Yang
2015-01-05  2:30 ` [meta-oe] [V2 PATCH 5/5] tomoyo-tools: use BP " Robert Yang
2015-01-05 11:59 ` [meta-oe] [V2 PATCH 1/5] dash: " Martin Jansa
2015-01-05 22:59   ` Robert Yang
2015-01-05 23:01     ` Robert Yang
2015-01-05 23:26     ` Martin Jansa
2015-01-06  0:07       ` Robert Yang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-05 23:45 MacDonald, Joe

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=54AB273E.4030600@windriver.com \
    --to=liezhi.yang@windriver.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.