Hi,

I didn't see anything about this issue so I apologize if it's been brought
up before and I just missed it. We have a situation where we need to point a
recipe at the latest code in a branch that at some point will see changes,
but is currently just an svn copy of code from the trunk. svn info shows the
last change as the last changed revision in the trunk, at a time when the
branch did not exist. This causes AUTOREV to get too old a revision and fail
to pull down the branch code. The latest message in svn log gets a useable
revision, so maybe AUTOREV could look at that instead. I can draw up a patch
later this week but I thought I'd put this change out there first and see
what people thought about it.

Thanks for your time,

Daniel Lazzari Jr.
[email protected]
_______________________________________________
Bitbake-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bitbake-dev

Reply via email to