Call for discussion: Phase names

Angel Ezquerra ezquerra at gmail.com
Tue Jan 17 14:43:19 CST 2012


On Jan 17, 2012 8:46 PM, "Matt Mackall" <mpm at selenic.com> wrote:
>
> On Tue, 2012-01-17 at 20:11 +0100, Pierre-Yves David wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> > On 17 janv. 2012, at 19:24, Matt Mackall wrote:
> >
> > > On Tue, 2012-01-17 at 09:58 +0100, Pierre-Yves David wrote:
> > >> Matt Mackall notified on IRC that the content of this discussion
convinced him to reconsider the rule "not have conflicting initials" and
replace "secret" by "private".
> > >>
> > >> The current naming scheme is now:
> > >>
> > >>    public / draft / private
> > >>
> > >> The according option will be
> > >>
> > >>    * --public (no short option)
> > >>    * -d --draft
> > >>    * -p --private
> > >
> > > Please only have long options.
> >
> > ???
> >
> > Since I've a phase enabled mercurial, I use "hg phase -fs" or "hg
> > phase -d" on regular basis ?
> >
> > What are your rational for removing short version ?
>
> Do you _really_ think we won't get bug reports that looks like this?
>
> "Hey, Mercurial is broken! I tried to do this:
>
> $ hg phase -p tip
> nothing changed
> $ hg phase tip
> draft
>
> Why won't this damn thing let me mark my changeset public???
> "
>
> If so, you're vastly overestimating the memory, patience, and
> meticulousness of the average software developer.
>
> (For the record, I try to use hg status -r or -c instead of --rev or
> --change on a weekly basis so I'm not about to accept any argument to
> the contrary.)
>
> Long options are the price of using private instead of secret as the
> phase name.
>
> --

Must the short options be the first letter of the long option?

If not, what about using the first vowel, which is different for each of
the phase names and also is easy to remember?

That is:

--public: -u
--draft: -a
--private: -I

cheers,

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120117/c5ab15a4/attachment.html>


More information about the Mercurial-devel mailing list