You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by David Waite <ma...@akuma.org> on 2002/07/23 06:33:32 UTC
property import/export
While conversing in #svn, Nicholas asked if there was a way to to
specify files to ignore on a svn import.
With CVS, imports pay attention to the .cvsignore, which allows you to
export a revision and import the tree into another repository. With
subversion, the ignore list is not a file but a property, and properties
do not get exported.
So there are a number of pieces of fruit here, some lower-hanging than
others:
a) It would be rather nice to be able to specify a file containing
ignore patterns when doing a 'svn import'. The difference between this
file and the svn:ignore property would be indicating ignore instructions
for subdirectories.
b) It would also be nice to be able to export this ignore list with 'svn
export'.
c) Eventually, importing and exporting the properties attached within
the repository would be ideal - although this would probably not be the
default, and a representation for this in a traditional filesystem would
need to be devised.
d) A patch format which could represent properties would be also be very
handy.
-David Waite
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: property import/export
Posted by David Waite <ma...@akuma.org>.
Nicholas Riley wrote:
>On Tue, Jul 23, 2002 at 03:10:37AM -0500, Eric Gillespie wrote:
>
>
>>David Waite <ma...@akuma.org> writes:
>>
>>
>>
>>>a) It would be rather nice to be able to specify a file containing
>>>ignore patterns when doing a 'svn import'. The difference between this
>>>file and the svn:ignore property would be indicating ignore instructions
>>>for subdirectories.
>>>
>>>
>>I was thinking about requesting cvs's -I option for similar reasons.
>>Would that satisfy your need? I'm not fond of the idea of ignored
>>files being specified in both a file and a property...
>>
>>
>
>I don't think David meant that the ignored files-in-a-file would
>persist once the initial import was complete, simply that they'd be
>read and used to direct file exclusion and property setting during the
>import.
>
>
Yep; its more how to specify properties like svn:ignore during import.
It grew a bit into a way to export and import properties, as you can
export and import files.
Another option would be to have an import-style command that does not
immediately commit files; it would instrument the directories for an
upcoming commit. Being able to import properties could then be done as a
script (but files which should have been ignored will then need to be
reverted before the initial commit).
<snip>
-David Waite
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: property import/export
Posted by Nicholas Riley <nj...@uiuc.edu>.
On Tue, Jul 23, 2002 at 03:10:37AM -0500, Eric Gillespie wrote:
> David Waite <ma...@akuma.org> writes:
>
> > a) It would be rather nice to be able to specify a file containing
> > ignore patterns when doing a 'svn import'. The difference between this
> > file and the svn:ignore property would be indicating ignore instructions
> > for subdirectories.
>
> I was thinking about requesting cvs's -I option for similar reasons.
> Would that satisfy your need? I'm not fond of the idea of ignored
> files being specified in both a file and a property...
I don't think David meant that the ignored files-in-a-file would
persist once the initial import was complete, simply that they'd be
read and used to direct file exclusion and property setting during the
import.
I had in mind a more general-purpose mechanism, something like the
.svn/dir-props and .svn/props/<filename> files, but with a simple XML
format, something like this:
<svn:property key="svn:ignore">build</svn:property>
with appropriate extensions if properties need to have MIME types or
binary encodings or similar. These XML-formatted property-import
files would be named <filename>.svnprops, read and automatically
assigned to the corresponding <filename> on import. After the initial
import, the .svnprops files would be discarded.
Support for specifiying svn:ignore (and no other properties) on import
would resolve my immediate annoyance, however. I don't like the -I
syntax because you have to provide it every time you do an import, and
it's a property of the import, rather than the tree you're importing,
so if you have a gigantic tree with lots of per-directory exclusions
you'll wind up with a gigantic command line.
--
=Nicholas Riley <nj...@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
Pablo Research Group, Department of Computer Science and
Medical Scholars Program, University of Illinois at Urbana-Champaign
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: property import/export
Posted by Eric Gillespie <ep...@pretzelnet.org>.
David Waite <ma...@akuma.org> writes:
> a) It would be rather nice to be able to specify a file containing
> ignore patterns when doing a 'svn import'. The difference between this
> file and the svn:ignore property would be indicating ignore instructions
> for subdirectories.
I was thinking about requesting cvs's -I option for similar reasons.
Would that satisfy your need? I'm not fond of the idea of ignored
files being specified in both a file and a property...
--
Eric Gillespie <*> epg@pretzelnet.org
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org