Hello,
Otherwise, you could also think the other way around. ie: "put what you
need" instead of "ignore what you don't need" first.
For example
svn mkdir %url2repo%projectX
svn checkout %url2repo%projectX .
add whatever file/folder you need (very easy with TortoiseSVN to cherry
pick, by selecting them).
then commit.
You can then set the svn:ignore property for the future.
JClaude
Ryan Schmidt a écrit :
>
> On Jan 29, 2008, at 06:53, Stefan Sperling wrote:
>
>> On Tue, Jan 29, 2008 at 10:11:15AM -0200, Marcelo de Moraes Serpa wrote:
>>
>>> I'm just adding a project for the first time to a repository
>>> (importing) and I don't want certain files and subdirs to be
>>> included. I thought on using the svn:exclude property but it can
>>> only be set on working copies and I don't have a working copy yet
>>> in this stage. What should I do ?
>>
>> You could temporarily move the certain files somewhere else,
>> do the import, and then move the files back.
>>
>> Another option would be to create a .svnignore file.
>> I cannot find where this is documented in the book,
>> but it should behave the same as .cvsignore.
>
> I'm not aware of a .svnignore file. The Subversion equivalent of the
> .cvsignore file is either the svn:ignore property, or the
> global-ignores section of the client-side config file.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-30 00:25:25 CET