From: Matt Mackall <mpm@selenic.com>
To: Soh Tk-r28629 <tksoh@freescale.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Mercurial List <mercurial@selenic.com>
Subject: Re: bitkeeper gone in 2 weeks - which RCS?
Date: Mon, 20 Jun 2005 17:29:55 -0700 [thread overview]
Message-ID: <20050621002955.GG27572@waste.org> (raw)
In-Reply-To: <0B3CDF75128AD5119E0800D0B782934E16BF94F9@zmy02exm01.ap.freescale.net>
On Tue, Jun 21, 2005 at 08:16:59AM +0800, Soh Tk-r28629 wrote:
> > -----Original Message-----
> > If you clone/init a repository from the source(or a mirror of it), you
> > get everything in it. If you want to then look at a specific revision of
> > the code, you: hg checkout -C [revision]
>
> How can I tell what revision is currently checked out this directory? 'hg id' seems to give too little information.
hg parents should help.
> Can I then make changes to this revision, then commit, and later update to tip? What are the commands to achieve this?
Almost. When you commit, your commit becomes the new tip. So you'll
need the heads command here to find the other head you want to merge
with.
hg commit
hg heads
hg up <id>
And this will usually imply a branch merge, so you'll need:
hg up -m <id>
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-06-21 0:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 0:16 bitkeeper gone in 2 weeks - which RCS? Soh Tk-r28629
2005-06-21 0:29 ` Matt Mackall [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 22:11 Ian Pratt
2005-06-16 1:16 ` Matt Mackall
2005-06-16 1:21 ` Rik van Riel
2005-06-15 23:03 ` Christopher Li
2005-06-16 11:36 ` Theodore Ts'o
2005-06-15 21:35 Ian Pratt
2005-06-15 21:45 ` Andrew Thompson
2005-06-16 2:56 ` Rusty Russell
[not found] ` <mailman.1118871375.26501@unix-os.sc.intel.com>
2005-06-16 18:34 ` Arun Sharma
2005-06-20 20:39 ` Paul Larson
2005-06-20 20:44 ` Rik van Riel
2005-06-20 20:54 ` Josh Triplett
2005-06-20 21:01 ` Andrew Thompson
2005-06-20 21:28 ` Paul Larson
[not found] ` <mailman.1119300279.12847@unix-os.sc.intel.com>
2005-06-20 21:03 ` Arun Sharma
2005-06-20 21:08 ` Rik van Riel
2005-06-15 19:45 Ian Pratt
2005-06-15 20:10 ` Rik van Riel
2005-06-14 19:09 Rik van Riel
2005-06-14 19:26 ` Paul Larson
2005-06-14 19:27 ` Ronald G. Minnich
[not found] ` <mailman.1118777276.15947@unix-os.sc.intel.com>
2005-06-14 19:43 ` Arun Sharma
2005-06-14 19:50 ` Paul Larson
2005-06-14 19:58 ` Arun Sharma
2005-06-14 23:31 ` aq
2005-06-14 23:50 ` Rusty Russell
2005-06-15 7:09 ` Michael Paesold
2005-06-16 2:37 ` Ronald G. Minnich
2005-06-16 11:51 ` David Hopwood
2005-06-15 19:18 ` Rik van Riel
2005-06-14 19:52 ` Ronald G. Minnich
2005-06-14 19:54 ` Arun Sharma
2005-06-15 7:51 ` Gerd Knorr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050621002955.GG27572@waste.org \
--to=mpm@selenic.com \
--cc=mercurial@selenic.com \
--cc=tksoh@freescale.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.