bound branch annoyances

[Marius Kruger]

Hi,
thanks for the responces

I don't know which bzr you're using,...
>
I always use the latest stable releases as I'm working on real life systems,
thus I'm rather safe than sorry.

If you uncommit in a checkout, you should expect to
> uncommit the revision from the branch you checked out.  Where else could
> you uncommit from?


The problem is when you are constantly switching between "heavyweight
checkouts"
and distributed branches, you never know which one you are dealing with,
(unless you check with 'bzr info' of coarse)

thus its easy to uncommit something you actually just wanted to do locally
(this actually happened when we temporarily wanted to uncommit something to
check
if some problems were caused by the latest revision. In this case we could
not readily get the original committer to get the commit again:( )


On 11/22/06, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
>
>
> >     Could we please have the commit message stored in some temp file for
> >     this kind of situations.
>
> Actually, wouldn't it be better if it fell back to 'commit --local' in
> this situation and warned to run 'update'?
>

PERFECT!!!
it saddens me to think that a brain like yours will have to rot one day :(
(thats intended as a compliment)


regards
marius
-- 



I code therefore I am.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20061122/411eb1fb/attachment.htm