Creating new IcedTea repos
Andrew John Hughes
gnu_andrew at member.fsf.org
Wed Feb 25 10:39:32 PST 2009
2009/2/25 Andrew Haley <aph at redhat.com>:
> Mark Wielaard wrote:
>> On Wed, 2009-02-25 at 16:38 +0000, Andrew John Hughes wrote:
>>> 2009/2/25 Lillian Angel <langel at redhat.com>:
>>>> Mark Wielaard wrote:
>>>>> On Tue, 2009-02-24 at 21:57 +0100, Mark Wielaard wrote:
>>>>>> hg-remote-clone got one additional feature, -r <rev> which lets you
>>>>>> clone a repository up to <rev> instead of the whole history of the
>>>>>> original repo. It can be used everywhere below, just as if doing a
>>>>>> normal hg clone -r. Please only use when needed, it is less efficient
>>>>>> than doing a full clone, so doing a full clone, or a -r tip one, is
>>>>>> preferred when you just want the full history for a branch.
>>>>> One oddity here which bit me while testing.
>>>>> Just like a normal hg clone, if you hg clone -r some-tag, it will clone
>>>>> up-to, but not include, the tag. That is because the tagging is just a
>>>>> normal commit, that adds the tag name and the (previous) revision number
>>>>> to the .hgtags file.
>>>>> So, if you want to include the tag, look in the hg log for the revision
>>>>> number one past the tag revision number itself.
>>>> This does not seem to be the case.
>>>> I created the minor release repo, like so:
>>>> ssh langel at icedtea.classpath.org hg-remote-clone -r 0641929711bf
>>>> /hg/icedtea6 /hg/release/icedtea6-1.4.1
>>>> And everything up to and including changeset 0641929711bf was added to the
>>>> repo, when I intended for only everything up to this changeset. This might
>>>> only be an issue when using the actual tag name.
>>> Yes, you get up to the changeset you specify and everything below,
>>> that's the expected behaviour.
>>> What Mark was referring to is if you use -r icedtea6-1.4 or such like.
>>> The resulting changeset doesn't have a copy of .hgtags with
>>> icedtea6-1.4 in it, because that's in the changeset after the one that
>>> was tagged.
>> Yes, I found that odd. But maybe that seems normal if you wrap your head
>> around it in some other way. I was just surprised. I would also have
>> assumed someone might want to create a branch from a tag name, like in
>> this case hg-remote-clone-r icedtea6-1.4 which would result in a branch
>> without the actual icedtea6-1.4 tag in it.
> So, you can't diff on the branch between the tag and the head ... then
> how do you find out what has changed on the branch? Hex revision ID?
No, so the best solution is presumably to merge the changeset with the
tag. But maybe there is something I've missed...
Note that the same changesets should be applied to the branch which
means hg export and hg import --exact. The hg transplant extension
Mark mentioned might be useful for this.
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev