##// END OF EJS Templates
checkheads: take future obsoleted heads into account...
checkheads: take future obsoleted heads into account If we push some successors they will likely create a new head on remote. However as the obsoleted head will disappear after the push we are not really increasing the number of heads. There is several case which will lead to extra being actually pushed. But this first changeset aims to be simple. See the inline comment for details. Without this change, you need to push --force every time you want to push a newer version which is very error prone. The remote side still display +n heads on unbundle because it does not have the obsolete marker at unbundle time.
Pierre-Yves David -
r17214:738ad56d default
Show More
Name Size Modified Last Commit Author
/ contrib
hgfixes
hgsh
macosx
plan9
vim
win32
wix
bash_completion Loading ...
buildrpm Loading ...
casesmash.py Loading ...
check-code.py Loading ...
convert-repo Loading ...
debugcmdserver.py Loading ...
debugshell.py Loading ...
dumprevlog Loading ...
hg-ssh Loading ...
hgk Loading ...
hgweb.fcgi Loading ...
hgweb.wsgi Loading ...
logo-droplets.svg Loading ...
memory.py Loading ...
mercurial.el Loading ...
mercurial.spec Loading ...
mergetools.hgrc Loading ...
mq.el Loading ...
perf.py Loading ...
pylintrc Loading ...
python-hook-examples.py Loading ...
sample.hgrc Loading ...
setup3k.py Loading ...
shrink-revlog.py Loading ...
simplemerge Loading ...
tcsh_completion Loading ...
tcsh_completion_build.sh Loading ...
tmplrewrite.py Loading ...
undumprevlog Loading ...
xml.rnc Loading ...
zsh_completion Loading ...