Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh 4.0.2 (powerpc-apple-darwin1.4)
- X-seq: zsh-workers 15969
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Oliver Kiddle <okiddle@xxxxxxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: Re: zsh 4.0.2 (powerpc-apple-darwin1.4)
- Date: Mon, 8 Oct 2001 09:53:13 +0000
- In-reply-to: <3BC174DA.782C7893@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20011008001533.A7577@xxxxxxxx> <000601c14fc2$afabdbd0$21c9ca95@xxxxxxxxxxxxxx> <9prhh5$drc$1@xxxxxxxxxxxxxxxxxxxxx> <3BC174DA.782C7893@xxxxxxxxxxx>
On Oct 8, 10:41am, Oliver Kiddle wrote:
}
} It isn't the case here but with some of the completion functions for
} example, the files are still identical on both branches. Is it possible
} to commit it as normal on the 4.1 branch and then just update the tag
} for the stable branch to the new file instead of copying and committing
} on the stable branch.
Unfortunately, no, CVS doesn't work like that.
If all you do is retag the trunk revision with an ordinary (non-branch)
tag, then checkouts of exactly that tag will pick up exactly that rev of
the file, but checkouts/updates of the branch tag will still get the
previous one.
You could manually delete and recreate the magic "branch tag", but that's
rather dangerous.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author