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

Re: Feature request and use case for --no-auto-props and --no-ignore checkboxes

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sun, 13 Mar 2011 08:55:22 +0100

On 02.03.2011 14:18, Catalin Iacob wrote:
> I would like to propose adding checkboxes for equivalents of
> --no-auto-props and --no-ignore for add and import operations. This
> has already been proposed in this thread[1] and Stefan decided not to
> do it. I think I have a good use case for this feature so maybe you'll
> reconsider.
> The --no-auto-props and --no-ignore options are very useful when you
> want to keep third party code in your SVN repositories. For my own
> code I have a big list of ignores and auto-props that I compiled in
> time and I always want to use it. But then I use some open source
> project that I want to bundle with my source for easy access,
> versioning etc. But when importing the third party code, I would very
> much prefer to leave it untouched. For example, a lot of times there
> are files with mixed line endings in the third party code and since my
> auto-props try to set svn:eol-style to native that ends up rejecting
> the files because of the mixed line endings. Or maybe some tests in
> the third party code depend on line endings being of a certain kind.
> If the checkboxes would be there, I would check them when adding third
> party code, now I have to fallback to using the command line client.
> What do you think? Is this good enough motivation to change your mind
> about the feature? I could even try implementing it.

Done in r20997.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-13 08:55:34 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

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