update N repos where N > 6

[Ivan Krylov]

Turned out that "hg clone source dest -u <tag>" is the same as "hg clone <source> <dest>"+"hg update <tag>".
See attached log.
I guess that even after clone -u tag the cloned repo still contains ALL tags and changesets and any accidental "hg update" will bring it to tip
Thanks,
Ivan





On Aug 21, 2013, at 4:35 AM, David Holmes <david.holmes at oracle.com> wrote:

> On 21/08/2013 2:38 AM, Ivan Krylov wrote:
>> Hi David,
>>
>> I also expected it to work out of the box.
>> I am attaching a log of what I did.
>> After "hg up jdk7u25-b34" on master and "clone master to dev" and "get_source.sh" on dev repo I expected to set HSX 23 but I got HSX24.
>> And this led me to my question.
>
> There is a difference between cloning another repo as-of a specific tag, and simply updating your working files to that tag. In the latter case your repo still has all changesets, hence a clone will also have all changesets.
>
> I think you need to use "hg clone -u <tag>" but then  you would not be able to use get_source.sh to clone the rest of the forest.
>
> David
>
>> Thanks,
>> Ivan
>>
>>
>>
>>
>>
>> On Aug 20, 2013, at 2:43 PM, David Holmes <david.holmes at oracle.com> wrote:
>>
>>> On 20/08/2013 7:59 PM, Ivan Krylov wrote:
>>>> This worked.
>>>> I was trying to update to revision instead of updating to tag and this didn't work for subrepos.
>>>>
>>>> Another related question (i hope this isn't far off topic): suppose I have my own master repository that I synced to a given tag.
>>>> I want all future clones made from my master to be also synced to the same tag without doing hg up <tag> in every child.
>>>> How to do so?
>>>
>>> Doesn't it "just work" like that. If your repo is the master and only pulled down the changesets up to a certain tag then I would expect any clones of that repo would be limited by the same tag.
>>>
>>> Easy enough for you to test.. :)
>>>
>>> David
>>>
>>>> Thanks,
>>>> Ivan
>>>>
>>>> On Aug 20, 2013, at 10:20 AM, Alexander Zuev <alexander.zuev at oracle.com> wrote:
>>>>
>>>>> Ivan,
>>>>>
>>>>>  instead of the separate repositories there are tags.
>>>>> List of tags can be seen at http://hg.openjdk.java.net/jdk7u/jdk7u-dev/tags
>>>>> So just clone the 7u-dev workspace and update it and all of the subrepositories to the desired tag
>>>>> (latest build number of the needed update release). For example for jdk7u8 tag is jdk7u8-b05.
>>>>> Just perform hg up jdk7u8-b05 in all the repos and you'll get it.
>>>>>
>>>>>  The online archives for all the openjdk mailing lists can be found at
>>>>> http://mail.openjdk.java.net/pipermail/<list_name>/
>>>>> For this list it's http://mail.openjdk.java.net/pipermail/jdk7u-dev/
>>>>> The full list of all the openjdk mailing lists can be found at
>>>>> http://mail.openjdk.java.net/mailman/listinfo
>>>>>
>>>>> With best regards,
>>>>> /Alex
>>>>>
>>>>>
>>>>> On 8/20/13 24:46, Ivan Krylov wrote:
>>>>>> Hello,
>>>>>>
>>>>>> How to get an 7updateN repository where 6 < N < 40?
>>>>>> There is no hg.openjdk.java.net/jdk7u/jdk7u25 repository as far as I see.
>>>>>>
>>>>>> This must have been discussed here many times before but I ma behind the times and searching online archives is painful )
>>>>>> BTW, what would be a good place to browse/search openjdk mail aliases archives?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Ivan
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cloning_not_from_a_tip.utf-8.2.txt
Url: http://mail.openjdk.java.net/pipermail/jdk7u-dev/attachments/20130821/1a581fdd/cloning_not_from_a_tip.utf-8.2.txt