From: Ryan Schmidt [mailto:subversion-2009a_at_ryandesign.com]
Sent: Wednesday, January 28, 2009 4:05 AM
Subject: Re: Ignoring certain versioned files during a commit
On Jan 3, 2009, at 01:41, postmaster_at_tigris.org wrote:
> I'm looking for a "hijack" functionality similar to that in
> ClearCase. Basically, when you mark a file as hijacked, changes to
> the file aren't sent to the server when you commit unless you clear
> the flag from the file.
> Does SVN have something similar? The file should still be
> versioned. This would be used when you want to play around with
> something and make sure it doesn't get accidentally committed.
I'm not sure of any direct functionality, but perhaps a changelist would
I don't think this applies exactly like you want - if you create a
changelist to keep your hijacked file separate, it'll still get
committed unless you create a changelist for all the other files and use
that when committing them.
Perhaps a slight modification to SVN would suit you: if you have a
changelist in operation, and files that are not categorised, then
committing would, by default, commit only those files that are not part
of the changelist (ie. think of all files being in a 'blank' changelist
by default, once you assign a file to a named changelist and commit the
'blank' one, the files assigned to the named changelist will not be
committed - which is the current behaviour). Alternatively, modify the
client to have another option "get as changelist x", where all files
retrieved to the working copy are assigned to the named changelist
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 15:23:47 CET