See the email thread "Don't release 'svn youngest'?" started on 2014-07-18,
archived at e.g. <http://svn.haxx.se/dev/archive-2014-07/0100.shtml> or
<http://mail-archives.apache.org/mod_mbox/subversion-dev/201407.mbox/%3C1405706747.13082.YahooMailNeo@web87701.mail.ir2.yahoo.com%3E>.
The text of the initial email follows.
Do we really want to release in 1.9 the 'svn youngest' command that has been
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?)
Bug
Major