[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 1807 - trunk trunk/subversion/clients/cmdline

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-04-27 20:41:01 CEST

sussman@tigris.org writes:

> Author: sussman
> Date: 2002-04-27 18:27 GMT
> New Revision: 1807
> After update or switch finishes, print "Updated to revision N."
> After checkout or URL->WC copy finishes, print "Checked out revision N."
> After merge finishes, don't print an extra line.

I should mention the rationale for the last behavior. When you run
'svn merge', you're not really updating your working copy to a
particular revision; instead, you're applying diffs between two
arbitrary paths and revisions. So it makes no sense to mention that
you've updated to anything in particular.

Also, regarding Greg Hudson's idea about

   U foo
   U bar
   # Updated to revision 5

I'm not sure we really need a comment character or anything like
that. We're certainly not using one when we do a commit:

   Sending foo
   Sending bar
   Committed revision 5

If people are worried about scripts being able to parse svn's output,
then it's just a matter of writing decent regexps.

In fact, you'll notice I didn't have to change a *single* bit of our
python tests for this change! It turns out that this is because the
function which parses the trace-editor's output is using a pretty
restrictive regular expression:

  rm = re.compile ('^(..)\s+(.+)')

In other words, I don't think we have any real problem here.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 27 20:44:12 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.