> Nathan Creek wrote:
>>> I think what is confusing here is that the files are listed as deleted
>>> but not added. To present a consistent picture to the user the list
>>> should read either:
>>>>> Sub2: deleted
>>>>> Sub2/File1.txt: deleted
>>>>> Sub2/File2.txt: deleted
>>>>> Subfolder/Sub2: added
>>>>> Subfolder/Sub2/File1.txt: added
>>>>> Subfolder/Sub2/File2.txt: added
> The problem here is that Subfolder/Sub2/File1.txt and
> Subfolder/Sub2/File2.txt have a Subversion status of
> svn_wc_status_normal and not svn_wc_status_added (!!?). You can easily
> see that when you use the CL client.
> But Sub2/File1.txt and Sub2/File2.txt have a status of
> svn_wc_status_deleted. Again, the CL client lists those as deleted too.
Ok. Good point. I have to admin i hadn't looked at what the CL client
showed, but now that i have i do notice that the addition of
Subfolder\Sub1 has a + (i havn't checked the docs, but i assume it
indicates recursive). So as a more simple change would it be possible to
add recursive in the status aswell?
Subfolder/Sub2: added (recursive)
>> Sub2: deleted (0 folders, 2 files)
>> Subfolder/Sub2: added (0 folders, 2 files)
> Well, just for having a little bit more information about something a
> developer _should_ know about anyway (if not, then giving such a
> developer commit access might be dangerous for the project!) this would
> just be too much work. Implementing that would require several days of
No worries. I'm not trying to make your life hard. I just figure it
doesn't hurt to make suggestions. I can accept no for an answer.
And as for giving commit access to potentially dangerous people. Maybe
it's just me, but in a small (<15 people) workplace environment I'd
rather give everyone commit access (including designers and documenters)
and just review their changes later than have them sending me patches
all day. It does mean that occasionally I have to deal with people who
can't understand why something works the way it does.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Nov 28 23:53:39 2004