blob: 74d5ad6911e64008c92bd9cb2c2ebb17816c3fa6 (
plain)
1
2
3
4
5
6
7
8
9
10
|
<br><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 2:32 PM, Thierry Vignaud <span dir="ltr"><<a href="mailto:thierry.vignaud@gmail.com">thierry.vignaud@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10 February 2012 22:08, trem <<a href="mailto:buildsystem-daemon@mageia.org">buildsystem-daemon@mageia.org</a>> wrote:<br>
> trem <trem> 1.1.0-0.r67830.1.mga2:<br>
> + Revision: 206947<br>
> - update to release 67830<br>
<br>
s/release/commit/ or revision...<br>
</blockquote></div><br><br>Well you obviously know the answer, so why not be a little more cheery and supportive.<br><br>Honestly trem there is away to know if something in each package directory actually changed. I don't think just because you did a blanketed svn up across the e trunk, that each package changed...<br>
<br>This is a little trick we've used for awhile LANGUAGE=C svn info | grep "Last Changed Rev:" | cut -d: -f 2 | sed "s@ @@"<br><br>a little example<br>cd edje<br>svn up<br>Updating '.':<br>
U src/lib/edje_program.c<br>.<br>.<br>.<br>U NEWS<br>Updated to revision 67845.<br>LANGUAGE=C svn info | grep "Last Changed Rev:" | cut -d: -f 2 | sed "s@ @@"<br>67833<br>
|
