#8 ✓resolved
Nicolas Dumazet

amp should not mess up the user ~/.hgrc

Reported by Nicolas Dumazet | November 24th, 2009 @ 01:17 PM

This is not acceptable, for obvious reasons.

Or, at the very least, APPEND to .hgrc, after a "append by amp" comment: do not modify existing sections.

It's perfectly fine to define several sections in the same .hgrc, hence making it possible to append without having to think to much.

As a side note: the current .hgrc is buggy. It adds a "requires" extension which does not exist, and activates win32mbcs on Unix platforms (useless, and adds a warning message on all hg runs)
inotify is buggy (I maintain it) and should not be activated. Where is that hgrc from?

Thanks.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Rethink Version Control.- http://amp.carboni.ca/

Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.

Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.

Shared Ticket Bins

People watching this ticket

Tags

Referenced by

Pages