[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] New branch name with no other changes
From: |
Stephen Leake |
Subject: |
Re: [Monotone-devel] New branch name with no other changes |
Date: |
Sun, 12 Jun 2011 04:24:35 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt) |
Richard Levitte <address@hidden> writes:
> In message <address@hidden> on Fri, 10 Jun 2011 16:40:59 +0200, Thomas Keller
> <address@hidden> said:
>
> me> Am 10.06.2011 16:26, schrieb Hendrik Boom:
> me> > Actually, the approve command worked fine, though it took a few moments
> me> > to determine the right revision ID. Maybe approving the revision in
> the
> me> > current workspace should be an option on that command? I wouldn't want
> me> > it to be the default: too easy to approve the wrong thing by accident.
> me>
> me> You could use
> me>
> me> mtn approve -b new.branch w:
> me>
> me> for the very same purpose and don't have to figure out the current rev
> me> id at all.
>
> But that places the current revision in the new branch as well. Was
> that Hendrik's intention, or was the intention that the next revision
> should end up in the new branch?
He said "it worked fine" :)
> What you'r forgetting, by the way, is that approve will not place the
> workspace in the new branch, so the next commit after that will end up
> in the original branch.
That is my process; I always create a new branch by adding a cert to an
existing revision, then checkout the branch into a new workspace, while
the current workspace remains on the original branch.
I maintain a strict correlation between workspace directory name and
branch name; I _never_ change the branch in an existing workspace (I
just find that confusing, and I often want to diff between branches to
see what has changed).
As Tony said, "with monotone you get to choose" :).
--
-- Stephe
- Re: [Monotone-devel] Improving documentation (was Re: New branch name with no other changes), (continued)
- Re: [Monotone-devel] Improving documentation (was Re: New branch name with no other changes), Thomas Keller, 2011/06/10
- Re: [Monotone-devel] Improving documentation, Richard Levitte, 2011/06/10
- Re: [Monotone-devel] Improving documentation, Aaron W. Hsu, 2011/06/10
- Re: [Monotone-devel] Improving documentation, Richard Levitte, 2011/06/10
- Re: [Monotone-devel] Improving documentation, Aaron W. Hsu, 2011/06/10
- Re: [Monotone-devel] Improving documentation, Stephen Leake, 2011/06/12
- Re: [Monotone-devel] Improving documentation, Aaron W. Hsu, 2011/06/12
- Re: [Monotone-devel] Improving documentation, Stephen Leake, 2011/06/12
- Re: [Monotone-devel] New branch name with no other changes, Richard Levitte, 2011/06/10
- Re: [Monotone-devel] New branch name with no other changes, CooSoft Support, 2011/06/11
- Re: [Monotone-devel] New branch name with no other changes,
Stephen Leake <=
- Re: [Monotone-devel] New branch name with no other changes, Hendrik Boom, 2011/06/12
- Re: [Monotone-devel] New branch name with no other changes, Stephen Leake, 2011/06/12
- Re: [Monotone-devel] New branch name with no other changes, Nuno Lucas, 2011/06/12
- Re: [Monotone-devel] New branch name with no other changes, Hendrik Boom, 2011/06/13
- Re: [Monotone-devel] New branch name with no other changes, CooSoft Support, 2011/06/16
- Re: [Monotone-devel] New branch name with no other changes, Hendrik Boom, 2011/06/16
- Re: [Monotone-devel] New branch name with no other changes, Richard Levitte, 2011/06/16
- Re: [Monotone-devel] New branch name with no other changes, Hendrik Boom, 2011/06/16
- Re: [Monotone-devel] New branch name with no other changes, Jerome Baum, 2011/06/16
- Re: [Monotone-devel] New branch name with no other changes, Stephen Leake, 2011/06/12