Hi Uwe,
You have orphans, so you should run `hg evolve`, I think.
Also, message text should be in the body of your message, not in an
attachment.
If you still think there is a problem, can you provide a script?
Regards, Faheem
___
Evolve-testers
>>> "PD" == Pierre-Yves David writes:
> The result you get is not the expected behavior (the result you want
> is the expected behavior).
I don't get the result which you call the expected.
Here is what I did
I pulled the latest hg-stable so actually I have
Mercurial Distributed SCM (version
>>> "PD" == Pierre-Yves David writes:
> latest version is 9.0.0 (however, the lastest verison with 4.4 support
> is 8.5.1 IIRC)
Thanks.
Here is what I did,
I changed to the evolve source directory which I had cloned already.
hg up 8.5.1
pip install --user .
Hg version -v
evolve
latest version is 9.0.0 (however, the lastest verison with 4.4 support
is 8.5.1 IIRC)
On 6/13/19 1:22 PM, Uwe Brauer wrote:
> hg version -v
Very useful thanks
evolve external 7.2.1
topic external 0.7.0
--
Pierre-Yves David
> hg version -v
Very useful thanks
evolve external 7.2.1
topic external 0.7.0
smime.p7s
Description: S/MIME cryptographic signature
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
hg version -v
On 6/13/19 1:09 PM, Uwe Brauer wrote:
"PD" == Pierre-Yves David writes:
The result you get is not the expected behavior (the result you want
is the expected behavior).
which versions or Mercurial and topic are you using ?
I am using mercurial 4.4.1 about the evolve
>>> "PD" == Pierre-Yves David writes:
> The result you get is not the expected behavior (the result you want
> is the expected behavior).
> which versions or Mercurial and topic are you using ?
I am using mercurial 4.4.1 about the evolve version I am not sure, since
I installed it via pip in
The result you get is not the expected behavior (the result you want is
the expected behavior).
which versions or Mercurial and topic are you using ?
On 6/13/19 12:06 PM, Uwe Brauer wrote:
Hi
In principle I like the fact that when I create a topic, I create a new
head (it annoyed but this
Lol I see :)
On Wed, Jun 12, 2019, 7:34 AM Pierre-Yves David <
pierre-yves.da...@ens-lyon.org> wrote:
>
>
> On 6/12/19 2:30 PM, Craig Ozancin wrote:
> >
> >
> > On Tue, Jun 11, 2019 at 3:44 PM Pierre-Yves David
> > mailto:pierre-yves.da...@ens-lyon.org>>
>
> > wrote:
> >
> > The difference
>>> "PD" == Pierre-Yves David writes:
> Right now, you can see them using `hg log --debug`. A simpler way to
> access the faded-away topic still need to be implemented.
Thanks! this is more or less what I was looking for. A pity that the nice
coloring is not seen.
A more visual solution would
Right now, you can see them using `hg log --debug`. A simpler way to
access the faded-away topic still need to be implemented.
On 6/13/19 11:24 AM, Uwe Brauer wrote:
"PD" == Pierre-Yves David writes:
> When you push to a publishing server, the changeset you push does not
> become
>>> "PD" == Pierre-Yves David writes:
> When you push to a publishing server, the changeset you push does not
> become obsolete, they become public. Once they are public, the topic
> data stop being display, but this is related to their phase, not to
> obsolescence.
Ok, but how
Hi
I enjoy the new (for me) topic extension quite a bit.
Would it be possible, at least optionally, not to make a topic
obsolescence after pushing to publishing repository?
Or is this against the whole philosophy of the topic extension?
(I know I could change the bitbucket repository to not
13 matches
Mail list logo
