Re: news from the topic experiment

Working on our Bitbucket spike I wondered if topics could perhaps benefit from a small simplification. Instead of adding the topic name as an additional field, what if we defined a topic commit by merely adding a boolean property to the meta dict; e.g. `is_topic: True`? Named branches would not

Re: news from the topic experiment

Gregory Szorc a écrit : There are still some areas for improving topics. 1) `hg log` still shows *all* changesets in the repository. This is confusing for users that don't want to be burdened with the complexity of multiple heads. I'd like the behavior of `hg log` to only show ancestors - and

Re: news from the topic experiment

> * `hg rebase` must be explicitly enabled. Some users think this means they > shouldn't be using it. Yeah as someone who is learning Mercurial I agree, usually I/people think that we need extensions when we are doing something which is not normal/general. > * `hg push` pushes all heads by

Re: news from the topic experiment

On Thu, Sep 22, 2016 at 5:26 PM, Augie Fackler wrote: > > > On Sep 22, 2016, at 8:18 PM, Pierre-Yves David < > pierre-yves.da...@ens-lyon.org> wrote: > > > >>> I assume this is along the spirit of your 'hg undo' for evolve (that > >>> preserves the hash)? > >> > >> No. We are

Re: news from the topic experiment

On Wed, Sep 28, 2016 at 8:20 AM, Pierre-Yves David wrote: > > > On 09/27/2016 05:44 PM, Long Vu wrote: >> >> Have not observed anything weird with missing obsolescence marker >> propagation, what symptom should we be paying attention to? > > If you pull from both

Re: news from the topic experiment

On 09/27/2016 05:44 PM, Long Vu wrote: On Tue, Sep 27, 2016 at 8:19 AM, Pierre-Yves David wrote: On 09/24/2016 03:21 AM, Long Vu wrote: I forgot a step. The final "release" is a push to master, followed by a push to the fork to propagate the public phase

Re: news from the topic experiment

On 09/23/2016 06:08 PM, Long Vu wrote: On Fri, Sep 23, 2016 at 11:50 AM, Long Vu wrote: I emulate git lightweight branching by basically using named branch with evolve and working on the fork of the "master" repo. We only enable evolve and non-publishing on the

Re: news from the topic experiment

On Wed, Sep 14, 2016 at 3:14 PM, Pierre-Yves David wrote: > > https://www.mercurial-scm.org/repo/topic-experiment/ > Sorry for jumping late to the discussion. I am a very happy Evolve user and so far I manage to basically replicate the lightweight branching of

Re: news from the topic experiment

Excerpts from Pierre-Yves David's message of 2016-09-23 02:43:37 +0200: > In the same way large organisation will probably want to define and > enforce naming scheme for topics. But they already need to do so today > for named-branch of git-branch. So nothing specific to topic here. For git,

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: 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

Re: news from the topic experiment

2016-09-20 15:39 GMT+02:00 Pierre-Yves David : > At this point, reference to non-publishing repository implies evolution > support. At some point evolution will stop being experimental and turned on > by default.  -- Demelier David

Re: news from the topic experiment

On 09/17/2016 08:21 AM, David Demelier wrote: 2016-09-16 18:35 GMT+02:00 Pierre-Yves David : This is a very valid feedback. The start of the topic experiments come from the finding that after 5 years of struggle trying to make bookmarks viable, they seems too

Re: news from the topic experiment

2016-09-14 21:14 GMT+02:00 Pierre-Yves David : > In the past couple of weeks I made a couple of extra changes to the topic > experiment, > > 'hg topic --verbose' got a large update and now list various information > about the topics, this should help people getting

Re: news from the topic experiment

On 09/15/2016 07:27 PM, Durham Goode wrote: On 9/14/16 12:14 PM, Pierre-Yves David wrote: Example output for messy state: ### topic: vfs.ward (2 heads) ### branch: default, 189 behind t7$ reposvfs: add a ward to check if locks are properly... (unstable) t6@ mq: release lock after transaction