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?) - Julian Julian Foad wrote on 2014-06-17: > Johan Corveleyn wrote: >> Julian Foad wrote: >> ... >>> Do we really want a new subcommand "svn youngest" for this? >>> >>> We already have: >>> >>> svnversion >>> # youngest rev in a WC >>> >>> svn info $URL | grep 'Revision:' >>> # head revision of repo in which $URL exists >> >> Not exactly. It would give you "Revision: 12345", not "12345". > > Yes. The point is, the information is already there... > >> I think it would be nice if 'svn info' supported a "key" option, so: >> >> svn info --key Revision $URL >> 12345 >> >> (or --name, or --whatever). >> >> Then we'd also have: >> >> svn info --key "Working Copy Root Path" some/path >> C:\MyWorkingCopy > > Yes: without selecting a specific colour to paint this bike shed, I like this > kind of interface. The "svn info" UI is already designed to display > this kind of information, so let's just make it display it in a more > convenient form rather than adding new subcommand for "youngest" and > then deciding whether to implement a new subcommand again for each additional > bit of info that we might like to access such as repo-UUID, file size, last > committed rev, and so on. > > Also: if the primary use case for adding 'svn youngest' was for use in > 'svnmucc' work flows, then maybe 'svnmucc' should be providing a > 'youngest' command or some other kind of solution to that particular > problem-space. > > - Julian >
