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

Re: Inconsistent way of showing added/deleted trees (?)

From: Mathias Weinert <mathias.weinert_at_gfa-net.de>
Date: 2006-03-01 17:26:41 CET

Max Bowsher wrote:

> Mathias Weinert wrote:
> > Referring to http://svn.haxx.se/dev/archive-2006-02/0853.shtml Max Bowsher wrote:
> >
> >> Looking at it now, I'm inclined to say that the difference between add
> >> and copy follows naturally from the intrinsic nature of those
> >> operations, and the inconsistency of delete sometimes showing children
> >> and sometimes not is just weird.
> >
> > A user doesn't know anything about the intrinsic nature of those
> > operations,
>
> I'm not referring to anything Subversion-specific here.
>
> Any user ought to be able to appreciate that "mkdir foo" creates an
> empty directory, whilst "cp -r src dest" creates a directory with
> whatever children existed in the copy source.

But in both cases the user only enters one command which creates
a new directory tree in the repository: 'svn add subdir' and
'svn cp src dst'. And in both cases 'svn ci' says 'Adding' so
he could expect to get the same information (i. e. all included
files and directories).

Maybe the client shouldn't say 'Adding' at commit time for copied
paths but 'Copying src to dst' or 'Adding ... (from...)' to make
the difference clear.
BTW, 'svn log' and 'svn st' already have different information
for copied paths: 'A ... (from..)' and 'A +'.

Anyway, I think this is not so important to spend too much time
on it. But perhaps at least the inconsistency of the delete
output may be resolved.

Mathias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 1 18:13:41 2006

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

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