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

How to specify just a prop change to "svn ci" and a feature request

From: Trent Mick <trentm_at_gmail.com>
Date: 2005-01-27 07:02:48 CET

Hello all,

Given the following (i.e. a property change on the current dir and a
file change on a file in that dir):

  $ svn status
   M .
  M relic.py

how does one tell "svn commit" to just commit the property change?
"svn ci ." doesn't work, obviously.

A feature that would help here (and in other circumstances) would be
for "svn ci" to allow one to control the set of things to commit by
editing the commit message template below this line:

  --This line, and those below, will be ignored--

I.e. in my case, it would be nice if I could delete the "M relic.py"
line that I get in the commit message to say "don't commit relic.py
yet, please".

You can do this kind of thing with Perforce. When you commit with
Perforce you get a form something like this:

        Change: new
        Client: <perforce-client-view-name>
        User: <username>
        Status: new
    
        Description:
            <checkin message goes here>
    
        Files:
            //depot/path/to/some/file.txt #edit
            //depot/path/to/some/other/file.txt #add

You can add or remove lines from the "Files" block to control what
files get commited to the repository. I can't remember if you can do
this with CVS as well (I don't think so.)

Does anyone know if this has been requested before? if I have missed
something obvious that allows this kind of thing in Subversion? Should
I add a feature request to the issue tracker?

Cheers,
Trent

-- 
Trent Mick
trentm@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 27 07:05:57 2005

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

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