per branch rules

Asked by Albert Visagie

Currently rules for determining line-ending filtering behaviour is stored/configured for particular user. There is no way to add it to a branch. Ideally it should work a bit like .bzrignore.

Reference: http://doc.bazaar.canonical.com/development/en/user-reference/eol-help.html

Noted that it is intended to work this way in a future version of bazaar, but it is kind of a show stopper for us.

Is there another way that I'm missing?

Question information

Language:
English Edit question
Status:
Answered
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Marius Kruger (amanica) said :
#1

Unfortunately this has not been implemented yet.
Because of foreign format concerns [1], instead of having it work like .bzrignore, the current thinking is more to make it work like tags.
ie. rather store branch specific rules in: .bzr/branch/rules ,
which means that it will not be copied as part of the workingtree when branching/pulling etc. (although I think that could be remedied) and also it will not be versioned.

[1] http://thread.gmane.org/gmane.comp.version-control.bazaar-ng.general/63732/focus=63738

Revision history for this message
Craig Hewetson (craighewetson-deactivatedaccount) said :
#2

I kind of like there to be inherited properties for bounded branches, rules of eof being one of them. (We work only with checkouts)
As requested here:
http://thread.gmane.org/gmane.comp.version-control.bazaar-ng.general/63732/focus=63738

Will one implementation of this work equally well for checkouts and unbound branches? (Don't have to answer this, its more of a thought I'm throwing out there)

Revision history for this message
Marius Kruger (amanica) said :
#3

> Will one implementation of this work equally well for checkouts and unbound branches?
yes

Can you help with this problem?

Provide an answer of your own, or ask Albert Visagie for more information if necessary.

To post a message you must log in.