- User Since
- Sep 30 2017, 6:32 AM (94 w, 1 d)
Apr 8 2019
Apr 5 2019
Jun 8 2018
May 30 2018
Feb 16 2018
lothiraldan (Boris Feld) wrote:
I have but I'm always very cautious when creating a new package with the
name of an old module. .pyc/.pycache files may still be there both for
Mercurial developers and for Mercurial users using their deb/rpm package.
I may be wrong, but if we could avoid weird bugs, I would prefer put in
the utils package.
Having both a util module and a utils package looks weird.
Have you considered moving util.py into util/__init__.py and then adding new modules under util package?
Feb 14 2018
Feb 11 2018
sangeet259 (Sangeet Kumar Mishra) wrote:
Feb 10 2018
Feb 9 2018
As mentioned in the issue, there's already an explanation paragraph in help:
Dec 8 2017
dlax (Denis Laxalde) wrote:
Also, would be nice to have some test coverage.
Dec 7 2017
Dec 6 2017
Dec 1 2017
In the future, the --inmemory flag might be deprecated in favor of something more intelligent
Nov 30 2017
pulkit (Pulkit Goyal) a écrit :
Nov 28 2017
Nov 24 2017
This rewriteutil.py introduced in this patch and the utility functions added in the upcoming patches exists in the evolve extension are being ported from there.
Nov 21 2017
Nov 17 2017
Nov 14 2017
Nov 13 2017
The state of this stack is not quite clear: there are abandoned revisions and the first changeset (introducing "mercurial/remotenames.py" file) seems to be missing.
LGTM modulo a few nits. Nice cleanup.
Nov 12 2017
For methods that are implemented, we change arguments to match the base.
Nov 11 2017
Nov 10 2017
Nov 3 2017
Oct 31 2017
Oct 19 2017
Oct 18 2017
Looks good to me, much nicer than the previous version.
Oct 17 2017
Oct 16 2017
This looks correct to me overall.
I use this feature with topics a lot and find it pretty convenient so I guess it might make sense for named branches in some workflows.
Oct 15 2017
Oct 14 2017
Apparently the "herald" thing did not work, sending again.