[Bug 6280] New: Vary HTTP header set on the wrong end of the connection

https://bz.mercurial-scm.org/show_bug.cgi?id=6280 Bug ID: 6280 Summary: Vary HTTP header set on the wrong end of the connection Product: Mercurial Version: unspecified Hardware: PC OS: Linux Stat

D6825: hgext: start building a library for simple hooks

joerg.sonnenberger updated this revision to Diff 20408. REPOSITORY rHG Mercurial CHANGES SINCE LAST UPDATE https://phab.mercurial-scm.org/D6825?vs=20371&id=20408 BRANCH default CHANGES SINCE LAST ACTION https://phab.mercurial-scm.org/D6825/new/ REVISION DETAIL https://phab.mercurial-

D8196: commit: clear resolved mergestate even if working copy is clean

martinvonz added a comment. In D8196#121923 , @pulkit wrote: > To me, having a `hg commit` which aborts, doing something seems a bit weird. Yes, I agree, as I said in the commit message. > For the use case of rebase, shelve etc., a

D8196: commit: clear resolved mergestate even if working copy is clean

pulkit added a comment. To me, having a `hg commit` which aborts, doing something seems a bit weird. For the use case of rebase, shelve etc., a function argument or internal config can be better. REPOSITORY rHG Mercurial CHANGES SINCE LAST ACTION https://phab.mercurial-scm.org/D8196/n