[PATCH 2 of 8 V3] addremove: warn when addremove fails to operate on a named path

Augie Fackler raf at durin42.com
Fri Dec 12 11:03:06 CST 2014


On Fri, Dec 12, 2014 at 04:49:26PM +0000, Martin von Zweigbergk wrote:
> On Thu Dec 11 2014 at 7:35:56 PM Matt Harbison <mharbison72 at gmail.com>
> wrote:
>
> > +#if windows
> > +  $ hg -v addremove nonexistant
> > +  nonexistant: The system cannot find the file specified
> > +  [1]
> > +#else
> > +  $ hg -v addremove nonexistant
> > +  nonexistant: No such file or directory
> > +  [1]
> > +#endif
> >
>
> I once used a glob in a case like this ("nonexistant: * (glob)"). It's
> shorter and should work on systems that produce yet another message, but
> it's also less specific. What do the more experienced Mercurial developers
> say? I haven't tried to search for examples myself (sorry).

I don't feel strongly one way or the other. Both seem fine.

> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel


More information about the Mercurial-devel mailing list