On Mon, Mar 11, 2002 at 02:41:10PM -0600, Ben Collins-Sussman wrote:
> "Jay Freeman \(saurik\)" <email@example.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.
I'm not sure if I got to commit, but if I did the --nonrecursive switch would
mean a directory and all its immediate file contents, but no subdirectories.
We really need --recurse-depth=[0|1|inf].
> > 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: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Mon Mar 11 23:59:01 2002
- application/pgp-signature attachment: stored