Re: [mxe-octave] Are hg pull and hg update required even at fresh hg clone?

[Tatsuro MATSUOKA]

----- Original Message -----

> From: Jordi Gutiérrez Hermoso 
> To: Tatsuro MATSUOKA 
> Cc: "octave-maintainers
> Date: 2016/5/23, Mon 10:10
> Subject: Re: [mxe-octave] Are hg pull and hg update required even at fresh hg 
> clone?
> 
> On Mon, 2016-05-23 at 09:43 +0900, Tatsuro MATSUOKA wrote:
>>  I am trying building octave using mxe-octave.
>> 
>>  I have found that fresh clone repo directory trees are not the latest one.
>>  I had to execute  
>> 
>>  cd (cloned directory)
>>  hg -v pull
>>  hg -v update
>> 
>> 
>>  to update the latest one.
>> 
>>  If it is true, description on the Wiki should be modified?
> 
> This happened because it the "@" bookmark keeps falling behind. By
> default, hg will update to the "@" bookmark, wherever it is. I just
> updated it again.
> 
> Some people update to a different revision and then do `hg update tip`
> instead of `hg update @` when they create a new commit. When this
> happens, the @ bookmark falls behind, because `hg update tip`
> deactivates the bookmark. This is not a grave problem. The bookmark
> should just be updated to where it should be.
> 
> It is useful to have this bookmark so that other bookmarks can be used
> for other heads of development. In this way, @ is the "master"
> bookmark, the one that is supposed to point to the current state of
> development.
> 
> - Jordi G. H.


OK. I understand.
However, I think that the wiki should be modified without "hg -v pull" and "hg 
-v update"
I have met errors.
I will edit it later and ask here whether my modification is valid.

Thanks!

Tatsuro