Re: news from the topic experiment

> On Sep 22, 2016, at 20:14, Jun Wu wrote: > > Excerpts from Sean Farley's message of 2016-09-22 17:30:34 -0700: >> Completely false. Take a look at the hgtopics repo: >> >> $ hg log --debug -vr 093a | grep "\(topic=\|phase\)" >> phase: public >> extra:

Re: news from the topic experiment

Pierre-Yves David writes: > On 09/23/2016 02:30 AM, Jun Wu wrote: >> Excerpts from Pierre-Yves David's message of 2016-09-23 02:01:11 +0200: >>> >>> On 09/22/2016 10:09 PM, Jun Wu wrote: Could we consider storing the topic of a changeset elsewhere so it's not

Re: news from the topic experiment

Excerpts from Sean Farley's message of 2016-09-22 17:30:34 -0700: > Completely false. Take a look at the hgtopics repo: > > $ hg log --debug -vr 093a | grep "\(topic=\|phase\)" > phase: public > extra: topic=stackheader I admit I didn't look into the details carefully. Sorry for

Re: news from the topic experiment

Excerpts from Jun Wu's message of 2016-09-23 01:30:28 +0100: > Excerpts from Pierre-Yves David's message of 2016-09-23 02:01:11 +0200: > > > > On 09/22/2016 10:09 PM, Jun Wu wrote: > > > Could we consider storing the topic of a changeset elsewhere so it's not > > > part of the changeset metadata?

Re: news from the topic experiment

Jun Wu writes: > Excerpts from Sean Farley's message of 2016-09-22 14:21:12 -0700: >> > Having topic in commit metadata makes it hard to rename them, and they are >> > not fundamentally different from branches imo - i.e. we can probably also >> > make branches work like the current

Re: news from the topic experiment

Excerpts from Pierre-Yves David's message of 2016-09-23 02:01:11 +0200: > > On 09/22/2016 10:09 PM, Jun Wu wrote: > > Could we consider storing the topic of a changeset elsewhere so it's not > > part of the changeset metadata? This will make it more lightweight and > > help preserve hashes with

Re: news from the topic experiment

> On Sep 22, 2016, at 8:18 PM, Pierre-Yves David > wrote: > >>> I assume this is along the spirit of your 'hg undo' for evolve (that >>> preserves the hash)? >> >> No. We are thinking about using topic to replace bookmark as the recommended >> workflow at fb.

Re: news from the topic experiment

On 09/22/2016 11:58 PM, Jun Wu wrote: Excerpts from Sean Farley's message of 2016-09-22 14:21:12 -0700: Having topic in commit metadata makes it hard to rename them, and they are not fundamentally different from branches imo - i.e. we can probably also make branches work like the current

Re: news from the topic experiment

On 09/22/2016 11:12 PM, Jun Wu wrote: Excerpts from Sean Farley's message of 2016-09-22 13:54:22 -0700: Jun Wu writes: Could we consider storing the topic of a changeset elsewhere so it's not part of the changeset metadata? This will make it more lightweight and help preserve

Re: news from the topic experiment

On 09/22/2016 10:09 PM, Jun Wu wrote: Could we consider storing the topic of a changeset elsewhere so it's not part of the changeset metadata? This will make it more lightweight and help preserve hashes with remote peers. One could definitely consider it. I've never been thrilled with having

Re: [PATCH 1 of 5] extdata: add extdatasource reader

> On Sep 22, 2016, at 13:21, Matt Mackall wrote: > > # HG changeset patch > # User Matt Mackall > # Date 1473794045 18000 > # Tue Sep 13 14:14:05 2016 -0500 > # Node ID 19bf2776dfe39befdc479253e1e7d030b41c08f9 > # Parent

Re: news from the topic experiment

Jun Wu writes: > Excerpts from Sean Farley's message of 2016-09-22 13:54:22 -0700: >> Jun Wu writes: >> >> > Could we consider storing the topic of a changeset elsewhere so it's not >> > part of the changeset metadata? This will make it more lightweight and >> >

Re: news from the topic experiment

Excerpts from Sean Farley's message of 2016-09-22 13:54:22 -0700: > Jun Wu writes: > > > Could we consider storing the topic of a changeset elsewhere so it's not > > part of the changeset metadata? This will make it more lightweight and > > help preserve hashes with remote peers. >

Re: news from the topic experiment

Could we consider storing the topic of a changeset elsewhere so it's not part of the changeset metadata? This will make it more lightweight and help preserve hashes with remote peers. Excerpts from Pierre-Yves David's message of 2016-09-14 21:14:16 +0200: > In the past couple of weeks I made a

[Bug 5378] New: hgrc points to the wrong place when using pooled clones

https://bz.mercurial-scm.org/show_bug.cgi?id=5378 Bug ID: 5378 Summary: hgrc points to the wrong place when using pooled clones Product: Mercurial Version: 3.8.2 Hardware: PC OS: Linux Status:

[PATCH 1 of 2 v4] dispatch: change indentation level in _dispatch()

# HG changeset patch # User Arun Kulshreshtha # Date 1474571988 25200 # Thu Sep 22 12:19:48 2016 -0700 # Node ID 75b224273359ed924528491efb88c612f3caa4ca # Parent 5271ae66615207f39cc41d78f4541bc6f8ca6ff6 dispatch: change indentation level in _dispatch() Add an if True:

mercurial@29989: 8 new changesets

8 new changesets in mercurial: http://selenic.com/repo/hg//rev/c89b55c8f936 changeset: 29982:c89b55c8f936 user:Anton Shestakov date:Wed Sep 21 19:52:48 2016 +0800 summary: gitweb: tweak branch table's last row's cell colspan on summary page

[Bug 5377] New: Enabling pager on interactive commands breaks them

https://bz.mercurial-scm.org/show_bug.cgi?id=5377 Bug ID: 5377 Summary: Enabling pager on interactive commands breaks them Product: Mercurial Version: default branch Hardware: All OS: All Status: UNCONFIRMED

Re: [PATCH 1 of 3 v2] profiling: allow nested usage of maybeprofile

On 9/22/16, 4:21 AM, "Yuya Nishihara" wrote: On Thu, 22 Sep 2016 09:04:40 +, Arun Kulshreshtha wrote: > On 9/21/16, 8:51 PM, "Yuya Nishihara" wrote: > Perhaps we can move both

[PATCH 5 of 5] extdata: pass contexts to hgweb templates

# HG changeset patch # User Matt Mackall # Date 1474310889 18000 # Mon Sep 19 13:48:09 2016 -0500 # Node ID e6e68432abcbeec0a74478f03762b0b3192c09b5 # Parent 6db1b2e7d19ed317404c1275db46780d40ececb8 extdata: pass contexts to hgweb templates This makes hgweb more in line

[PATCH 1 of 5] extdata: add extdatasource reader

# HG changeset patch # User Matt Mackall # Date 1473794045 18000 # Tue Sep 13 14:14:05 2016 -0500 # Node ID 19bf2776dfe39befdc479253e1e7d030b41c08f9 # Parent 5271ae66615207f39cc41d78f4541bc6f8ca6ff6 extdata: add extdatasource reader This adds basic support for extdata, a

[PATCH 2 of 5] extdata: add revset support for extdata

# HG changeset patch # User Matt Mackall # Date 1474293900 18000 # Mon Sep 19 09:05:00 2016 -0500 # Node ID 9c8847df32a0c5045e60aded2e03a9c97507f909 # Parent 19bf2776dfe39befdc479253e1e7d030b41c08f9 extdata: add revset support for extdata This inserts extdata into the

[Bug 5376] New: hg log -pf FILE does not print patches sometimes when it should

https://bz.mercurial-scm.org/show_bug.cgi?id=5376 Bug ID: 5376 Summary: hg log -pf FILE does not print patches sometimes when it should Product: Mercurial Version: default branch Hardware: All OS: All

[PATCH remotenames-ext] tests: fix failures related to double->single quote changes

# HG changeset patch # User Kostia Balytskyi # Date 1474562531 25200 # Thu Sep 22 09:42:11 2016 -0700 # Node ID 3aa5c4dbf5086615dbbe42b0d2d9fd5ca0488cf1 # Parent 7a6c5ff76f225c8ebe9baef9d5ef753da915aa8b tests: fix failures related to double->single quote changes diff --git

[PATCH evolve-ext] evolve: fix the way evolve checks whether dirstate.write has arguments

# HG changeset patch # User Kostia Balytskyi # Date 1474560467 25200 # Thu Sep 22 09:07:47 2016 -0700 # Branch stable # Node ID ac125f907dfe8f85d0c2771b3f71eaec788d9ea0 # Parent 8f902ec9ed9a296d92c2c2df1536af8c44b5321c evolve: fix the way evolve checks whether dirstate.write

[PATCH 1 of 2] graphlog: preserve topo sort even if additional filter options specified

# HG changeset patch # User Yuya Nishihara # Date 1474545233 -32400 # Thu Sep 22 20:53:53 2016 +0900 # Node ID 63cfb37603c39abe9e7ef58462c39dd1bb83c2df # Parent 5271ae66615207f39cc41d78f4541bc6f8ca6ff6 graphlog: preserve topo sort even if additional filter options specified

[PATCH 2 of 2] log: drop outdated optimization to walk revisions in reverse order

# HG changeset patch # User Yuya Nishihara # Date 1474545564 -32400 # Thu Sep 22 20:59:24 2016 +0900 # Node ID ffd93984937821bf449e2596acdb15a2c4ee88af # Parent 63cfb37603c39abe9e7ef58462c39dd1bb83c2df log: drop outdated optimization to walk revisions in reverse order Since

[PATCH 5 of 9 V2] manifest: specify checkambig=True to revlog.__init__, to avoid ambiguity

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548718 -32400 # Thu Sep 22 21:51:58 2016 +0900 # Node ID f41572305dfab3686526fcc3a1339689542b6b53 # Parent 770044f70593a8f3932e176784ed09e33d734ddf manifest: specify checkambig=True to revlog.__init__, to avoid

[PATCH 1 of 9 V2] scmutil: factor out common logic of delayclosedfile to reuse it

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548716 -32400 # Thu Sep 22 21:51:56 2016 +0900 # Node ID f2f665437a4939b06d9d03ae70f41f51bc5338f4 # Parent 5271ae66615207f39cc41d78f4541bc6f8ca6ff6 scmutil: factor out common logic of delayclosedfile to reuse

[PATCH 6 of 9 V2] changelog: specify checkambig=True to avoid ambiguity around truncation

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548719 -32400 # Thu Sep 22 21:51:59 2016 +0900 # Node ID 550a2388d189a079822ee13d901f3cb9854e5a3e # Parent f41572305dfab3686526fcc3a1339689542b6b53 changelog: specify checkambig=True to avoid ambiguity around

[PATCH 8 of 9 V2] repair: open a file with checkambig=True to avoid file stat ambiguity

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548720 -32400 # Thu Sep 22 21:52:00 2016 +0900 # Node ID 338febde64d5fe6a5aac79aff54741e201b5d88f # Parent 5ec24143ad2e85bf1567d9af83df9fc5187f0a4e repair: open a file with checkambig=True to avoid file stat

[PATCH 3 of 9 V2] vfs: use checkambigatclosing in checkambig=True but atomictemp=False case

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548717 -32400 # Thu Sep 22 21:51:57 2016 +0900 # Node ID 012c44bc655e19121818ab0c3e34bf610a6dc1cf # Parent 6b0eb9c2264b6fe8d4d70dfe15c600058d9f0f41 vfs: use checkambigatclosing in checkambig=True but

[PATCH 7 of 9 V2] changelog: specify checkambig=True to revlog.__init__, to avoid ambiguity

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548719 -32400 # Thu Sep 22 21:51:59 2016 +0900 # Node ID 5ec24143ad2e85bf1567d9af83df9fc5187f0a4e # Parent 550a2388d189a079822ee13d901f3cb9854e5a3e changelog: specify checkambig=True to revlog.__init__, to

[PATCH 9 of 9 V2] transaction: open a file with checkambig=True to avoid file stat ambiguity

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548720 -32400 # Thu Sep 22 21:52:00 2016 +0900 # Node ID c47d67e9412df24914ff4caaf1437a2c35a0af6b # Parent 338febde64d5fe6a5aac79aff54741e201b5d88f transaction: open a file with checkambig=True to avoid file

[PATCH 4 of 9 V2] revlog: specify checkambig at writing to avoid file stat ambiguity

# HG changeset patch # User FUJIWARA Katsunori # Date 1474548718 -32400 # Thu Sep 22 21:51:58 2016 +0900 # Node ID 770044f70593a8f3932e176784ed09e33d734ddf # Parent 012c44bc655e19121818ab0c3e34bf610a6dc1cf revlog: specify checkambig at writing to avoid file stat

Re: [PATCH 1 of 3 v2] profiling: allow nested usage of maybeprofile

On Thu, 22 Sep 2016 09:04:40 +, Arun Kulshreshtha wrote: > On 9/21/16, 8:51 PM, "Yuya Nishihara" y...@tcha.org> wrote: > Perhaps we can move both maybeprofile() calls to _dispatch() without > thinking > about how nested profilers behave. > >

Re: [PATCH 1 of 3 v2] profiling: allow nested usage of maybeprofile

On 9/21/16, 8:51 PM, "Yuya Nishihara" wrote: On Wed, 21 Sep 2016 18:07:57 +, Arun Kulshreshtha wrote: > On 9/21/16, 7:41 AM, "Yuya Nishihara" wrote: > > maybeprofile() can be called in threads. If we need to