Non-recursive commits don't work?

[Scott Palmer <sc...@2connected.org>]

I'm using 1.1 RC4 on windows XP at the moment and noticed something 
strange.

Usually when I issue "svn ci" in a workiing directory all my changes 
are commited recursively.  Today I had a need to commit changes in a 
particular folder, but not any sub-folders.

I did:

svn ci -N -m "fixed bug xxxx"

...and there was no output from the command at all, "svn st" showed 
that the files in that folder were still modified, as were a couple 
files in a sub-folder.

I also tried putting a dot '.' for the current directory after the 
above (svn ci -N -m "blah" .) but that had the same effect.

I had to manually specify the files I wanted to check in to get them 
committed without the changes from the sub-folder.

e.g.:

svn ci -m "fixed bug xxxx"  file1.java  file2.java

worked fine.

Did I do something wrong in the first case with the -N parameter?  Or 
did I find a bug?

The output of  "svn st" before I did the commit looked like this:
M  folder/blah1
M  folder/blah2
M  file1
M  file2

It was unaffected by my non-recursive attempts, but after my successful 
attempt it showed that what I wanted to do did indeed happen:
M  folder/blah1
M  folder/blah2

I expected -N to do the trick, as if there were many files in the 
current folder it would have been rather tedious to check them all in 
in one revision.

Scott


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Non-recursive commits don't work?

[Scott Palmer <sc...@2connected.org>]

On Oct 6, 2004, at 12:52 PM, C. Michael Pilato wrote:

> Scott Palmer <sc...@2connected.org> writes:
>> I did:
>>
>> svn ci -N -m "fixed bug xxxx"
>>
>> ...and there was no output from the command at all, "svn st" showed
>> that the files in that folder were still modified, as were a couple
>> files in a sub-folder.
>
> 'commit' is the only svn subcommand for which -N means "depth 0 --
> directory only" instead of "depth 1 -- directory and its non-directory
> children".
>

Ahhhh...

Feature request:  avoid special cases :)

Perhaps a -D (depth) argument or something similar would be useful to 
allow commit to work like everything else. E.g.  -D0 directory only, 
-D1 the directory and the files in it...

Scott


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Non-recursive commits don't work?

["C. Michael Pilato" <cm...@collab.net>]

Scott Palmer <sc...@2connected.org> writes:

> I'm using 1.1 RC4 on windows XP at the moment and noticed something
> strange.
> 
> Usually when I issue "svn ci" in a workiing directory all my changes
> are commited recursively.  Today I had a need to commit changes in a
> particular folder, but not any sub-folders.
> 
> I did:
> 
> svn ci -N -m "fixed bug xxxx"
> 
> ...and there was no output from the command at all, "svn st" showed
> that the files in that folder were still modified, as were a couple
> files in a sub-folder.

'commit' is the only svn subcommand for which -N means "depth 0 --
directory only" instead of "depth 1 -- directory and its non-directory
children".

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org