qrebase extension
Matt Mackall
mpm at selenic.com
Wed May 7 12:07:37 CDT 2008
On Wed, 2008-05-07 at 12:25 -0400, Gregory Collins wrote:
> Gilles Moris <gilles.moris at free.fr> writes:
>
> > On Tue May 6 2008 16:55:51 Gregory Collins wrote:
> >> If something were to go wrong with the merge this has the potential for
> >> losing work. In my local copy I'm going to do something like:
> >>
> >> ui.write(_("\nBackup queue saved to %s\n") % newpath)
> >>
> >> instead. Backup behaviour should perhaps be a configuration option?
> >>
> >> G.
> >>
> >
> > That's a pertinent request.
> > What would you think of an --backup=yes|no option that would default to yes,
> > and may be to false later when the code is stabilized.
> >
> > That way, it could be configurable in the default section oh hgrc:
> > [defaults]
> > qrebase = --backup=yes
>
> That sounds good to me, although from configuring other extensions I was
> expecting something like:
>
> [qrebase]
> backup=True
>
> To Matt: in general, what are the "best practices" for configuring
> extensions? The wiki seems to be mum on the subject.
What Gilles is suggesting is the generic approach for adding command
line defaults, which means no work for him. If that's not sufficient,
adding a section for the extension is the usual way to go.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list