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

Re: RFC: svn update --print-log-messages

From: Ketil Z. Malde <ketil_at_ii.uib.no>
Date: 2002-12-19 10:01:26 CET

ketil@ii.uib.no (Ketil Z. Malde) writes:

> "B. W. Fitzpatrick" <fitz@red-bean.com> writes:
>
> > > $ svn up
> > > U notes/autoversioning-strategy.txt
> > > Updated from revision 1066 to revision 1234.
>
> > Hmmm. I like the idea, but what should Subversion do in the case of a
> > mixed revision working copy?
>
> 1. Use the oldest one. I think this is (normally?) the same as
> 2. Use the current directory version
>
> This way, we err on the safe side, and a subsequent 'svn log' would
> get a few superflous log messages.
>
> 3. Print multiple notification
>
> $ svn up
> U notes/autoversioning-strategy.txt
> Updated from revision 1066 to revision 1234.
> U new/alternatives.txt
> U new/more-alternatives.txt
> Updated from revision 1100 to revision 1234.

3b. Print multiple version numbers

        $ svn up
        U this
        U that
        U the other
        Updated from revision(s) 1066,1100 to 1234

(Or will the list become too long? It will normally only affect
committed files, won't it? And most people will update regularly
- won't they?)

Okay, I'll shut up now. :-)

-kzm

-- 
If I haven't seen further, it is by standing in the footprints of giants
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 19 10:12:27 2002

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