Dear Bob and TortoiseSVN Users,
Here's an example...
Create an empty repository and check out a working copy.
Set svn:global-ignores to "*.asv *.tmp" at the top level (with a newline
between those two patterns if it matters).
Now, mkdir "theFiles", cd "theFiles", touch a.m a.asv b.m b.asv c.tmp
d.tmp e.tmp f.tmp
Right-click on the WC and choose commit. You see this dialog...
Notice how all the *.asv and *.tmp files still show up, even though the
intent of the svn:global-ignores was that they not be versioned.
Choose "Add" on the "theFiles" folder and you see this:
again, all those *.tmp and *.asv files have been selected by default,
even though the svn:global-ignores property on the parent folder shows
that they aren't desirable files.
Finally, if we add just the "theFiles" folder and nothing else, then the
commit dialog looks like this:
My suggestion is that the TortoiseSVN Commit and Add dialogs should
filter the list of files in unversioned child folders according to the
svn:global-ignores that would be active if that child folder were added.
I understand that the current behaviour is perhaps "right" in some sense
- but even so, I don't think it is helpful. The display is cluttered
with junk files and it is easy to accidentally add a file that should be
being ignored.
Best wishes,
Chris.
On 21/08/2013 18:15, Bob Archer wrote:
>> Dear TortoiseSVN team,
>>
>> First, thank you for all your efforts to provide such a great tool.
>>
>> Now, my suggestion is regarding the handling of the new svn:global-ignores
>> feature for folders that have not yet been added to the repository.
>>
>> At the moment, until a folder is "added", the svn:global-ignores filter is not
>> applied.
> I'm not sure what you are saying here? Are you saying that you can't apply a property to a folder that is NOT versioned? If so, that is correct.
>
>> Instead, it would be great if svn:global-ignores could be used to hide files in
>> sub-folders even before they are added.
> Since the folder isn't yet versioned, there is no way to apply a property to it. I'm not sure how this could ever work.
>
> Generally, global ignores are done at the project or repository level... that the whole point of them, so you don't have to add svn:ignore to every new folder, you can put an svn:global-ignores at your project root and it would apply to anything you are adding under that path recursively, including when using the import command.
>
> BOb
>
>
>
>> Finally, on a related note, at the moment clicking "ignore" on a file fails if the
>> parent folder hasn't yet been added. Could TortoiseSVN offer to add the folder
>> and re-attempt setting the ignore in that case?
>>
>> Best wishes,
>>
>> Chris.
>>
>> ------------------------------------------------------
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageI
>> d=3063072
>>
>> To unsubscribe from this discussion, e-mail: [users-
>> unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3063250
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-23 16:49:41 CEST