This revision now requires changes to proceed.
baymax added a comment.
baymax requested changes to this revision.
There seems to have been no activities on this Diff for the past 3 Months.
By policy, we are automatically moving it out of the `need-review` state.
Please, move it back t
lothiraldan added a comment.
In https://phab.mercurial-scm.org/D2679#73347, @martinvonz wrote:
> Here's a case I just ran into where I would have liked to de-obsolete a
commit:
>
> 1. Someone queues a patch and pushes to central repo. Repo looks like this:
You are using the wo
martinvonz added a comment.
Here's a case I just ran into where I would have liked to de-obsolete a
commit:
1. Someone queues a patch and pushes to central repo. Repo looks like this:
o B
|
o A
2. I fix a typo and and amend, but I forget to push.
3. I build m
markand added inline comments.
INLINE COMMENTS
> configitems.py:1041
> )
> +coreconfigitem('ui', 'localobsolescence',
> +default=True,
https://www.mercurial-scm.org/wiki/UIGuideline#naming_config_options
REPOSITORY
rHG Mercurial
REVISION DETAIL
https://phab.mercurial-scm.org/D2679
To
lothiraldan added a comment.
In https://phab.mercurial-scm.org/D2679#70935, @durin42 wrote:
> In https://phab.mercurial-scm.org/D2679#70934, @lothiraldan wrote:
>
> > In https://phab.mercurial-scm.org/D2679#69388, @durin42 wrote:
> >
> > > I'm slowly becoming convinced that the lon
durin42 added a comment.
In https://phab.mercurial-scm.org/D2679#70934, @lothiraldan wrote:
> In https://phab.mercurial-scm.org/D2679#69388, @durin42 wrote:
>
> > I'm slowly becoming convinced that the long-unquestioned axiom that "all
markers are distributed globally" isn't correct,
lothiraldan added a comment.
In https://phab.mercurial-scm.org/D2679#69388, @durin42 wrote:
> In https://phab.mercurial-scm.org/D2679#68489, @lothiraldan wrote:
>
> > To take a step back, I'm wondering what's the end goal? I remember there
was a discussion about having rebase enabled
durin42 added a comment.
In https://phab.mercurial-scm.org/D2679#68489, @lothiraldan wrote:
> To take a step back, I'm wondering what's the end goal? I remember there
was a discussion about having rebase enabled by default, is it related?
Getting rebase (and maybe histedit?) enabl
lothiraldan added a comment.
Hi Pulkit,
Thanks for your patience. I had a couple of important things to get out of
the way before I could turn my attention to this.
I reached out to Ryan and he sent me the code he wrote at the 4.6 Sprint. I
made it available here to support the disc
pulkit added a comment.
Hey @lothiraldan, if not the patches itself, can you please explain the
approach taken?
If I don't hear from you this week, I will push this series so that we can
have enough time testing this in current cycle. Thanks!
REPOSITORY
rHG Mercurial
REVISION DETAIL
h
pulkit added a comment.
@lothiraldan Gentle reminder for the series you were talking about.
REPOSITORY
rHG Mercurial
REVISION DETAIL
https://phab.mercurial-scm.org/D2679
To: indygreg, #hg-reviewers
Cc: lothiraldan, pulkit, mercurial-devel
___
M
pulkit added a comment.
In https://phab.mercurial-scm.org/D2679#64079, @lothiraldan wrote:
> In https://phab.mercurial-scm.org/D2679#62662, @pulkit wrote:
>
> > These patches were result of a very extensive discussion about what ways
we have to start supporting obsmarkers by default.
lothiraldan added a comment.
In https://phab.mercurial-scm.org/D2679#62662, @pulkit wrote:
> These patches were result of a very extensive discussion about what ways we
have to start supporting obsmarkers by default. I will like to push these
changesets so that we can try these in this c
pulkit added a comment.
These patches were result of a very extensive discussion about what ways we
have to start supporting obsmarkers by default. I will like to push these
changesets so that we can try these in this cycle. If I don't hear any concern
in a week, I will push them.
REPOSITOR
indygreg created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.
REVISION SUMMARY
Our path to enable obsolescence/evolve in core is to enable
creation of markers locally (no exchange) with user-facing behavior
that mimics existing behavior as
15 matches
Mail list logo