summaryrefslogtreecommitdiffstats
path: root/AUTHORS
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2013-10-31 17:36:25 -0700
committerPaul Eggleton <paul.eggleton@linux.intel.com>2013-12-03 17:12:14 +0000
commit91e3735c2e73094b49f99b01008bb5bf47dacf04 (patch)
treeff4e17015f19b2b0c04eb93b1d2b016ae3143727 /AUTHORS
parentbbb4fa427739912ff3b87379bf629066f6662458 (diff)
downloadbitbake-91e3735c2e73094b49f99b01008bb5bf47dacf04.tar.gz
fetch2/svn.py: use log instead of info to retrieve revision
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. (Bitbake master rev: 17d8ef0b813a05c231e3dbe6e8bc82a4a9b1d2f8) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions