Am Mittwoch, den 26.09.2007, 10:08 +0000 schrieb Paolo Borelli:
> I set some ignores in my local bzr branch and when I pushed I noticed
> that the .bzrignore file ended up in the svn repo. I think .bzrignore
> should be special cased so that it is not committed in the svn repo.
>
> Turning what is set in .bzrignore into svn:ignore properties would be
> extra sweet, but it's really secondary since if I am using bzr-svn
> chances are that the svn:ignore are already properly set.
This is impossible until there is a 1-to-1 mapping for .bzrignore and
svn:ignore properties. Imagine a situation where somebody push a
revision to subversion from Bazaar that adds a .bzrignore file. If
somebody else then pulls that revision, they don't get the .bzrignore
file (because it was never added to Subversion) and thus end up with a
corrupt revision.
I'll mark this as a duplicate of the bug requesting for svn:ignore
support.
Am Mittwoch, den 26.09.2007, 10:08 +0000 schrieb Paolo Borelli:
> I set some ignores in my local bzr branch and when I pushed I noticed
> that the .bzrignore file ended up in the svn repo. I think .bzrignore
> should be special cased so that it is not committed in the svn repo.
>
> Turning what is set in .bzrignore into svn:ignore properties would be
> extra sweet, but it's really secondary since if I am using bzr-svn
> chances are that the svn:ignore are already properly set.
This is impossible until there is a 1-to-1 mapping for .bzrignore and
svn:ignore properties. Imagine a situation where somebody push a
revision to subversion from Bazaar that adds a .bzrignore file. If
somebody else then pulls that revision, they don't get the .bzrignore
file (because it was never added to Subversion) and thus end up with a
corrupt revision.
I'll mark this as a duplicate of the bug requesting for svn:ignore
support.
Cheers,
Jelmer samba.org/ ~jelmer/
--
Jelmer Vernooij <email address hidden> - http://
Jabber: <email address hidden>