emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locks on the Bzr repository


From: Jan Djärv
Subject: Re: Locks on the Bzr repository
Date: Sat, 21 Aug 2010 12:47:41 +0200
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2



Eli Zaretskii skrev 2010-08-21 12.41:
Date: Sat, 21 Aug 2010 12:30:44 +0200
From: Jan Djärv<address@hidden>

This is correct.  However any bzr operation like a simple C-x v = fails
because bzr is locked by the commit (it doesn't seem to do read-only locks).
That is the main disadvantage that makes me go back to the task branch.

I agree that this is a disadvantage, but is it really that
significant?  How much do you use bzr operations while developing?
Most of development is not about bzr, it's about editing, compiling,
and testing.  I only need bzr operations when I'm almost done with
development, like to see what files are changed or compare them with
some other version.  No matter how slow is "bzr ci" upstream, the
development cycle is much slower, at least for me.  It can only be
faster if you fix very simple bugs, like typos.

YMMV, but this disadvantage doesn't sound a reason good enough to make
a cardinal decision to do all the work from a task branch.

It depends on your mode of programming I think. Most of the time it doesn't matter. But sometimes while searching for a bug, I put debug messages in several files (more often so when I am in an area I have little knowledge of). Or I make what I think are the correct changes, but then it turns out I was mistaken. So I want to remove some of the changes. C-x v = or C-x v d helps me find them. For new stuff I don't use bzr that much, if at all.

        Jan D.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]