<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/13/2014 01:42 AM, Pierre-Yves
David wrote:<br>
</div>
<blockquote cite="mid:52D3B517.5030207@ens-lyon.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 01/12/2014 02:25 PM, Sean Farley
wrote:<br>
</div>
<blockquote
cite="mid:b97f7e3553f1694abd36.1389565552@laptop.local"
type="cite">
<pre wrap=""># HG changeset patch
# User Sean Farley <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:sean.michael.farley@gmail.com"><sean.michael.farley@gmail.com></a>
# Date 1383779296 21600
# Wed Nov 06 17:08:16 2013 -0600
# Node ID b97f7e3553f1694abd360e30c0e4a9eac59f393a
# Parent 460212c85977dbeec5007558fa26293a4a0d11f4
merge: include obsolete calculation for branchtips
Previously, a bare update would ignore any successor changesets thus
potentially leaving you on an obsolete head. This happens commonly when there
is an old bookmark that hasn't been moved forward which is the motivating
reason for this patch series.
Now, we will check for successor changesets if two conditions hold:
1) we are doing a bare update
2) *and* the branchtip returned normally is obsolete</pre>
</blockquote>
<br>
<small><small><small><big><big><big>This is a </big></big></big></small></small></small>slghlty
different version of what we discussed in New-York.<br>
<br>
2) should be "if current working directory parent is a head and
obsolete"<br>
<br>
If update can move up along standard topology it should alway just
do it.<br>
</blockquote>
<br>
This is actually even more different, This patch update to tipmost
foreground. You want to update to tip most successors set in that
case.<br>
<br>
<br>
-- <br>
Pierre-Yves<br>
<br>
<br>
</body>
</html>