WorkingTree doesn't expose API for ignore/unignore

Bug #44725 reported by Jeff Bailey
4
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Wishlist
Unassigned

Bug Description

WorkingTree provides interfaces to tell if a file is ignored or not, but doesn't expose an API to twiddle that setting.

Robert said on IRC that he considered this to be a bug, so I'm filing it as such.

Tks,
Jeff Bailey

Revision history for this message
John A Meinel (jameinel) wrote :

Agreed. Right now the only way is to write .bzrignore directly. And this is extra bad if we decide to use a different layout in the future.

Changed in bzr:
status: Unconfirmed → Confirmed
Revision history for this message
Dan Watkins (oddbloke) wrote :

The way ignores work currently, as I understand them, is that .bzrignore gets read in when it is needed. It is cached internally until unlock() is next called, when the cache is cleared.

If we allow manipulating of ignore definitions through the WorkingTree, we will need to write the definitions back out when unlock() is called. What happens if .bzrignore has been edited between the locking and unlocking?

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.