# HG changeset patch
# User Faheem Mitha <fah...@faheem.info>
# Date 1526734596 -19800
# Sat May 19 18:26:36 2018 +0530
# Branch stable
# Node ID 31a5c06bea822b58db8d77d23edea7832ae301c5
# Parent 4a70392f1723c9e31d8b7fa68b2fc942d024901d
debian: add line to clean-docs target to
patch?
I've also posted this on Stack Overflow -
https://stackoverflow.com/q/49219477/350713
Please CC me on any reply. Thanks in advance.
Regards, Faheem Mitha
#!/bin/sh
cd /tmp
hg init test
cd test
echo "This is foo" >> foo
hg add
hg ci -m "
First reported Mercurial bug circa 2005.
Faheem Mitha
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
med branch to default, the named branch is obsoleted, and
one can forget about it. I think this would work for my purposes. But
is there anything I am missing that makes named branches an unsuitable
choice for this purpose?
Thanks in advance for any replies.
Regards, Fa
of
branch or topic name and give a warning if they differ on unshelve?
See for example https://bz.mercurial-scm.org/show_bug.cgi?id=6123.
Regards, Faheem Mitha
#
shelveinterrupt.sh
#
#!/bin/bash
rm -rf test-shelveinterrupt
hg init test-shelvein
On Sat, 6 Nov 2021, Craig Ozancin wrote:
It is possible to pull both branches and bookmarks using the -b / -B
options. Is there any way to specifically pull a topic?
hg init test
cd test
hg pull -r topicname reposname
works for me here. That will pull everything up to the topic
t peculiar to
be trying to use something for temporary use that is designed for
permanent use. I'm not sure what to think about topic, but at least
it's designed for that purpose.
Regards, Faheem Mitha
On 11/03/2019 19:57, Faheem Mitha wrote:
Hi folks,
I've been using Evolve for some time. One
med branch to default, the named branch is obsoleted, and
one can forget about it. I think this would work for my purposes. But
is there anything I am missing that makes named branches an unsuitable
choice for this purpose?
Thanks in advance for any replies.
Regards, Fa
ckage,
which you can see in the development version of the README, at
https://bitbucket.org/octobus/evolve-devel. Comments welcomed, of
course.
Regards, Faheem Mitha
Uwe
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
https://www.m
On Fri, 14 Jun 2019, Faheem Mitha wrote:
On Fri, 14 Jun 2019, Uwe Brauer wrote:
> On Fri, 14 Jun 2019, Uwe Brauer wrote:
> It's fairly easy to obtain a Debian package for Mercurial. In many
> cases, the Debian package from unstable will install on testing or
On Fri, 14 Jun 2019, Uwe Brauer wrote:
> On Fri, 14 Jun 2019, Faheem Mitha wrote:
> DEB_BUILD_OPTIONS="nocheck" make deb
Bash or tcsh?
I don't know about tcsh. But try it.
___
Evolve-testers mailing list
Evolve-t
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
On Fri, 14 Jun 2019, Uwe Brauer wrote:
Hi Faheem
> Hi Uwe,
> On Fri, 14 Jun 2019, Uwe Brauer wrote:
> You need to run `hg evolve --any` multiple times, not once.
Thanks again. I did more experiments.
Mercurial 4.4 + evolve 8.5.1: does not work
Mercurial 5 + evolve 8.5.1: does work
On Sat, 27 Apr 2019, Friedrich Hagedorn wrote:
Hello,
I tried the metaedit command from the evolve extension and was happy to
find a nearly convenient way to refactor the commit messages of my
recent commits. In order to metaedit the changesets with branched
ancestors together with an unclean
On Mon, 6 May 2019, Faheem Mitha wrote:
Hi folks,
I'm not sure if this is a bug, so writing here first.
I thought this might have something to do with topics, but apparently not,
since if I comment out the topic line, I get the same behavior.
This is all quite strange. Either I'm really
, restoring its
predecessor.
Comments/clarifications/corrections appreciated. I can post a bug report if
necessary - let me know. Thanks.
Regards, Faheem Mitha
rm -rf rewind
hg init rewind
cd rewind
touch a
hg add a
hg ci -m
?
Regards, Faheem Mitha
I have to think about it.
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
it's a bug, of course.
Anyway, good work. Bugs aren't necessarily easy to reproduce.
Regards, Faheem Mitha
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
Hi Anton,
On Sun, 17 Oct 2021, Anton Shestakov wrote:
On Sun, 17 Oct 2021 00:45:46 +0530 (IST)
Faheem Mitha wrote:
10.4.0 is currently not showing up in the tags for the Evolve repos at
https://www.mercurial-scm.org/repo/evolve/. The most recent version is
10.3.3.
This was unfortunately
, what is the new address?
Thanks.
Regards, Faheem Mitha
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
, Faheem Mitha
On Thu, 25 Nov 2021, Uwe Brauer wrote:
Hi
I am really confused. I am still on Ubuntu 16.04 with python 3.5
So far I have compiled for example mercurial 5.2 with python 2.7 and used
evolve by just putting
evolve =
In my .hgrc
Now I compiled mercurial 5.5 with python3.5
So I
On Sat, 6 Nov 2021, Craig Ozancin wrote:
It is possible to pull both branches and bookmarks using the -b / -B
options. Is there any way to specifically pull a topic?
hg init test
cd test
hg pull -r topicname reposname
works for me here. That will pull everything up to the topic
Hi Christopher,
On Wed, 21 Jul 2021, Christopher Speck wrote:
I originally posted this in the Mercurial mailing list but found
there’s a separate one for Evolve. I’ve come across an issue while
using the evolve extension where running a `rebase` command
unexpectedly does not result in a new
. What's the problem with that? What
different behavior would you prefer?
Note that metaedit does have the -m (message) option, which would
presumably replace the existing commit message, though I have not tested
that. But that's generally not what you want to do.
Regards, Faheem Mitha
Hi Marco,
See below.
On Fri, 7 Apr 2023, Marcos Cruz wrote:
Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T22:18:48+0530):
Yes, normally metaedit is intended to edit the existing commit message.
Hence it's natural to open an editor. What's the problem with that?
I'm converting my
Hi Marcos,
On Fri, 7 Apr 2023, Marcos Cruz wrote:
Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T23:39:45+0530):
If you just want to change the user or date of the commit, there are
separate flags for that. Namely, -u, -U, -d, and -D.
Have you not looked at the help? See below
committing. See EDITOR.
(deprecated, see 'hg help config.ui.editor')
Regards, Faheem Mitha
___
Evolve-testers mailing list
evolve-test...@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
of new versions of Evolve
recently. The last announcement of 10.5.3 was on Monday 12th December
2022. Is there any reason for this, or just that nobody has taken the time
to do it?
Regards, Faheem Mitha
___
Evolve-testers mailing list
evolve-test
Hi Anton Shestakov,
See below.
On Thu, 25 May 2023, Anton Shestakov wrote:
25.05.2023 09:41, Faheem Mitha пишет:
Hi folks,
I'm currently running Mercurial 6.3, and was thinking of upgrading to 6.4.
I was just wondering what the correct version of Evolve to upgrade to was.
It looks from
is quite buggy.
Regards, Faheem Mitha
___
Evolve-testers mailing list
evolve-test...@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
30 matches
Mail list logo
