RetroSearch Browse

Fri Dec 16 22:16:03 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-December/058854.html

Hi Phillip,

On Fri, Dec 16, 2005 at 11:33:00AM -0500, Phillip J. Eby wrote:
> >Not if you're happy with "Last Changed Rev":
> >
> >     LC_ALL=C svn info | grep -i "last changed rev" | cut -f 4 -d " "
> 
> You left off the all-important "-R" from "svn info", and the "sort -nr | 
> head -1" at the end.  The "Last Changed Rev" of the root is not necessarily 
> the highest "Last Changed Rev", no matter how or where you update or check 
> out.  Try it and see.

I was proposing this line as a slight extension of the one currently in
the SF patch.  In accordance with Martin I am still unconvinced that
'svn info -R' or more fancy tools are really useful here.

If you meant that the following situation is possible:

    trunk$  svn up
    At revision xxx.
    trunk$  svn info
    Last Changed Rev: 10000
    trunk$  cd Python
    trunk/python$  svn info
    Last Changed Rev: 10001

then I object.  As far as I can tell this is not possible.

A bientot,

Armin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/058854.html below:

[Python-Dev] Expose Subversion revision number to Python