On Thu, Sep 23, 2010 at 12:43 AM, David Huang <khym_at_azeotrope.org> wrote:
>
> On Sep 22, 2010, at 8:21 PM, Chris Albertson wrote:
>> But, I did not think until now that I should have excluded files such
>> as core files and logs and autoconf's cache from version controls. I
>> now know how to a global ignore and a ignore foe one directory but how
>> to remove these files from version control once they are already
>> there. Is "svn rm" the best why? But that will remove them from
>> the working directory too. I don't want that.
>
> svn rm --keep-local filename
Which is thoughtful, but does *NOT* get old versions of the file out
of the repository. Unfortunately, that's been requested before, and
has never gotten into working code that I can find. The idea is called
"obliterate", and it goes against the basic design ideas of the
creators of Subvresion: a source control is supposed to keep all your
source, not allow obliteration whether accidental or deliberate by
users.
Obliterating it, as things stand, would require taking the upstream
repo offline, doing an "svnadmin dump | svndumpfilter [arguments] |
svnadmin load" set of operations, and it's awkward.
>> Next is these a way to make the ignore property for a directory apply
>> to all sub dirs recursively. The next project I want to move to svn
>> is much larger and has many nested directories
>
> svn propset --recursive svn:ignore ignorepattern .
Also, the very nice "TortoiseSVN" gui is fabulous for doing just such
operations. It's my only excuse these days for doing any Windows work
with Subversion: the tool works really well.
Received on 2010-09-23 13:40:41 CEST