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

Re: How to invert the svn:ignore meaning?

From: Talden <talden_at_gmail.com>
Date: 2007-09-10 22:52:07 CEST

Perhaps add an "svn:notice" that accepts patterns in the same way as
svn:ignore the only difference being that its absence is treated as
containing the all-inclusive '*' and the client 'notices' files that
are in the svn:notice set but not in the svn:ignore set.

So for existing repos there is no difference but if 1.5+ were to add
this support to its client then people could begin to express
expectations about the versionable content of certain folders.

As always the client could bypass this with a force and already
versioned files would always be noticed.

Though you could get even more expressive. Consider a simple svn:flags
property for things like

ignore_modification - so a versioned file once added is ignored for
the purposes of commit and status.

revert_on_update - an extension to 'ignore_modification' that would
restore the state of a 'statically versioned file'.

I think there are quite a few useful 'svn:' properties that the client
could consume whose absence retains the current behaviour (and so
should not upset users who do not exercise use-cases requiring them).

If we're already reading the properties to check for svn:ignore then
I'm assuming the client cost would be almost non-existent in the
absent cases - of course that depends upon the lookup mechanism which
I know nothing about.

--
Talden
On 9/9/07, Luca Ferrari <fluca1978@infinito.it> wrote:
> On Friday 7 September 2007 ANGonline's cat, walking on the keyboard, wrote:
> > So I'd like to avoid versioning of those uninteresting (to me) file.
> > I found that svn:ignore can help me to avoid the versioning of known
> > *unwanted* file pattern while I olny now the pattern of *wanted* file: *.h
> > *.c *.m.
>
> Not sure if this is what you want and is the best way of doing: supposing you
> can run scripts (like shell scripts) you can traverse your tree examinating
> each file and making an add only of those that interest you. For instance in
> bash something like this:
>
> #!/bin/bash
> # invoke with the tree root
> cd $1
>
> for f in *
> do
>    if [ -f $f ]
>    then
>     case $f in
>       *.h | *.c | *.m) svn add $f;;
>       *) ;;
>      esac
>     else
>     if [-d $f]
>     then
>          $0 $f
>     fi
> done
>
> Hopes this help.
>
> Luca
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 10 22:48:54 2007

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

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