.bzrignore should be converted to svn:ignore

Bug #145155 reported by Paolo Borelli on 2007-09-26
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned
Bazaar Subversion Plugin
Wishlist
Unassigned

Bug Description

It should be possible to map .bzrignore into svn:ignore properties and back in a reproducible fashion

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
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Jelmer Vernooij (jelmer) on 2007-09-26
Changed in bzr-svn:
assignee: nobody → jelmer
importance: Undecided → Wishlist
status: New → Triaged
description: updated
Jelmer Vernooij (jelmer) on 2008-07-25
Changed in bzr-svn:
milestone: 0.5.0 → none
Jelmer Vernooij (jelmer) wrote :

In order for this to be doable, .bzrignore needs to be moved out of the working tree in bzr and have a particular API. (i.e. it should have a situation similar to signatures/inventories)

Jelmer Vernooij (jelmer) wrote :

At the moment we're treating tree metadata as actual data and that means we'll end up with two copies of the ignores in subversion (one in .bzrignore, one in their file properties) to import from. Importing from svn after that becomes hard because it means you have to do merging and potential conflict resolution.

Having .bzrignore as data also means we have to be able to regenerate the .bzrignore file from the svn properties with the exact same contents each time and with ordering preserved. A non-workingtree-file could not have any restrictions wrt ordering.

Finding the ignores is also O(tree) right now since the ignores file would have to be generated on the fly.

There was another issue, but I seem to've forgotten that one.

Jelmer Vernooij (jelmer) on 2008-07-28
Changed in bzr-svn:
milestone: none → 0.5.0
Vincent Ladeuil (vila) on 2008-09-05
Changed in bzr:
importance: Undecided → Wishlist
status: New → Triaged
Jelmer Vernooij (jelmer) on 2008-12-09
Changed in bzr-svn:
milestone: 0.5.0 → 0.6.0
Jelmer Vernooij (jelmer) on 2009-04-11
Changed in bzr-svn:
milestone: 0.6.0 → none
Jelmer Vernooij (jelmer) on 2009-06-14
Changed in bzr-svn:
milestone: none → 2.0.0
Martin Pool (mbp) on 2010-03-19
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer) on 2011-02-10
Changed in bzr-svn:
assignee: Jelmer Vernooij (jelmer) → nobody
Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions