Creating new IcedTea repos

[Andrew John Hughes]

2009/2/25 Lillian Angel <langel at redhat.com>:
> Mark Wielaard wrote:
>>
>> Hi,
>>
>> On Tue, 2009-02-24 at 21:57 +0100, Mark Wielaard wrote:
>>
>>>
>>> On Mon, 2009-02-23 at 23:09 +0100, Mark Wielaard wrote:
>>>
>>>>
>>>> One bottleneck working on IcedTea was that it wasn't easy to create new
>>>> repos or clone existing ones. That has now been solved. Everybody who
>>>> can push to IcedTea can now clone repos for release or private (but
>>>> public) branches, or create new repos for work related to IcedTea that
>>>> they want to host (the only requirement is that the work is Free
>>>> Software of course).
>>>>
>>>
>>> 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.

>
>
>
>>
>>>>
>>>> When creating a release repo from on of the main repos under /hg do:
>>>>
>>>> ssh <repo>@icedtea.classpath.org \
>>>>  hg-remote-clone /hg/<repo> /hg/release/<repo>-x.y
>>>>
>>>> Please do coordinate first on the version string/extension used.
>>>> Release branches will show up under http://icedtea.classpath.org/hg/ and
>>>> have a release/ prefix.
>>>>
>>>> When creating a repo for a private repo under your own /people/<user>/
>>>> tree do:
>>>> hg init ssh://<user>@icedtea.classpath.org/people/<user>/<repo-name>
>>>>
>>>> Or if you already have a local repo then you can push it through:
>>>> hg clone <repo-name> \
>>>>  ssh://<user>@icedtea.classpath.org/people/<user>/<reponame>
>>>>
>>>> But if it is work based on an existing repo (either
>>>> under /hg, /hg/release or /people/<someone>/) then please do a server hg
>>>> clone to safe bandwidth and disk-space on the server by:
>>>>
>>>> ssh <repo>@icedtea.classpath.org \
>>>>  hg-remote-clone /hg/<repo> /people/<user>/<repo-name>
>>>>
>>>> These personal repos will also show up under
>>>> http://icedtea.classpath.org/people/ and will have your <user> name
>>>> and / as prefix.
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>>
>>
>>
>
>



-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8