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

Re: svn commit: r19645 - branches/changelist-feature/subversion/svn

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-05-15 19:30:58 CEST

On 5/15/06, sussman@tigris.org <sussman@tigris.org> wrote:
> Author: sussman
> Date: Mon May 15 10:27:12 200
>
> Log:
> Make 'svn status' display grouped changelists.

After reading through the extremely long thread about how 'svn status'
formatting should look, I just committed code to my branch which makes
'svn status' display changelists by groups. Here's why.

   * Everyone prefers the visual appearance, it's more friendly to see
     a "group" of paths meant to be committed together as, well, a group!

   * It doesn't endanger streaminess or increase memory usage much, as
     I originally thought it would. 'svn status' already holds all of
     a wc's entries in memory at once, thanks to the entries-caching
     feature. So adding a bit of 'buffering' doesn't change the
     memory footprint significantly.

   * Yes, it it changes the way 'svn st' must be parsed, but

     - the new format *only* shows up if users start marking files as
       being part of changelists.

     - apps truly dependent on parsing can resort to --xml for safety.

Here's some Sample output from my actual working copy:

$ svn st
? 1.2-backports.txt
? floo.txt
? 1.3-logs.txt
? notes/changelist.txt
M notes/wc-improvements

Changelist 'junk':
M README

Changelist 'status-cleanup':
M subversion/svn/main.c
M subversion/svn/info-cmd.c

Changelist 'status-printing':
M subversion/svn/status-cmd.c

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 15 19:32:30 2006

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.