All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH RFC] fetch2/svn.py: use log instead of info to retrieve revision
Date: Tue, 5 Nov 2013 21:17:36 +0800	[thread overview]
Message-ID: <5278EFF0.7010601@windriver.com> (raw)
In-Reply-To: <CAP71Wjz8DXdFYqMER6uy+7X9ic-PJmGQVp+d5ayC4TJ5Eqgozw@mail.gmail.com>



On 11/05/2013 02:48 AM, Nicolas Dechesne wrote:
> On Thu, Oct 31, 2013 at 5:36 PM, Nicolas Dechesne
> <nicolas.dechesne@linaro.org> wrote:
>> We have faced a corner case situation where the 'last changed
>> revision' returned from svn info is wrong. It happens when the last
>> revision is a directory move. e.g. if we assume that the svn
>> repository at revA has root/x/y/z/foo/bar and it is moved to
>> root/a/b/c/foo/bar in revB, then svn info 'last change revision' will
>> return revA. As such when using AUTOREV, we are going to attempt to
>> retrieve root/a/b/c/foo/bar (as per SRC_URI) but at revA when it did
>> not exist.
>>
>> So this patch changes how we retrieve the latest revision and uses
>> 'svn log --limit 1' which gives correct result in all tested cases.
>
> Richard, thanks for merging in master. any chance this can go to dora

Hi Nicolas,

I will add it to the queue of dora, thanks.

// Robert


> and dylan too, as this is a bug fix? the same patch applies in both
> branches, and we are currently using dylan and dora for our projects.
>
> thanks
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
>


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  0:36 [PATCH RFC] fetch2/svn.py: use log instead of info to retrieve revision Nicolas Dechesne
2013-11-04 18:48 ` Nicolas Dechesne
2013-11-05 13:17   ` Robert Yang [this message]
2013-11-07 16:26   ` Paul Eggleton

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=5278EFF0.7010601@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=nicolas.dechesne@linaro.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.