On 18.07.2014 20:05, Julian Foad wrote: > Do we really want to release in 1.9 the 'svn youngest' command that was > introduced recently? > > There are several kinds of 'youngest' rev we might want to ask for, and we > already have the following ways of asking for several of them: > > svn info URL | grep 'Revision:' > # head rev of repo > > svn info URL | grep 'Last Changed Rev:' > # youngest last-committed rev in subtree at URL (with bubble up) > > svnversion WC_PATH > # range of base revs in subtree at WC_PATH > > svnversion --committed WC_PATH > # range of last-committed revs in subtree at WC_PATH > > while 'svn youngest' only tells us one of them: the youngest rev in the > repository. > > Can I ask that we use one of these three other UIs instead. > > 1. > > Add a convenient way to get a single field from 'svn info', as has been > proposed several times before. > > 2. > > Add an 'svnmucc youngest' subcommand instead, since I understand that the > primary motivation was for users of 'svnmucc'. > > 3. > > svnversion URL > # head rev of repo > > svnversion -c URL > # range of last-committed revs in subtree at URL > > These correspond pretty closely to the existing WC target variants of > 'svnversion', and also provide similar information to the two uses of 'svn > info URL'. > > (Peg revisions should also be supported and should change the meaning to 'the > last revision <= peg rev'. And before anybody points out that 'svnversion' > has never been linked to RA code, I pre-emptively ask: so what?)
+1 to all of that. -- Brane -- Branko Čibej | Director of Subversion WANdisco | Realising the impossibilities of Big Data e. br...@wandisco.com
