When manually resolving directory conflicts isn't a feature

[Maritza Mendez]

Make that "bzr switch" not "bzr branch" of course!

On Sun, Apr 5, 2009 at 10:47 PM, Maritza Mendez <martitzam at gmail.com> wrote:

>
>
> On Sun, Apr 5, 2009 at 6:43 PM, Mary Gardiner <mary at puzzling.org> wrote:
>
>> I wanted to raise this here rather than filing bugs as I have a suspicion
>> they'd be marked invalid-that's-a-feature like bug 102001.
>
>
> I've seen this happen with every good version control system I've used.
> (Don't ask what the bad ones did!)  I don't mean to defend what bzr is
> doing, but it sounds like "bzr branch" is causing you more trouble than it
> is saving.  It's been many years since I used (La)TeX -- but complex
> software projects generate far more files you don't want to version than TeX
> and metafont combined.  Is there a reason you don't just use separate
> working trees?  I've always thought that switching the branch a checkout
> points to is a workflow best suited to minor variations within a project.
> It sounds like you are switching between dramatically different projects.
> Using separate trees also has the advantage that I can multitask between
> projects without being slowed down by my tools.
>
> I'm just sharing my experience and not trying to change your mind.  Good
> luck in your dissertation.
>
> -M
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090405/37028fb0/attachment.htm