"Jay Freeman \(saurik\)" <saurik@saurik.com> writes:
>
> Directory A contains File B. A has a property change, B has a modification.
>
> I wanted to commit the property change to A, and I was just blndly copying
> and pasting the entries from an "svn status" that I wanted to commit, so I
> listed the directory name as an argument to commit. I didn't want to commit
> the file modification as I knew it was bogus.
We have --nonrecursive switch; looking at 'svn help commit', it seems
that it's not a valid option to commit right now. I wonder why not?
Maybe Pilchie or someone else can let us know whether this switch
can/should work with commits.
> On a related note, I found it difficult to mentally keep track of the
> changes I was making to directory properties. I usually do an "svn diff"
> before I check files into the repository so I can see that only the changes
> I really want get to the server, and being unable to do something like a
> "propdiff" gets irritating.
? If you run 'svn status', it will print an 'M' in the second column
for items that have property mods. But yeah, it's a little annoying
that you can't *see* the property diffs. I think we could list 'svn
propdiff' as a new bite-sized task for someone...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 11 21:38:53 2002