On Fri, Sep 05, 2008 at 09:24:54AM -0700, Stephen Lau wrote: > timeless wrote: > > On Wed, Sep 3, 2008 at 7:33 PM, Mark J. Nelson<[EMAIL PROTECTED]> wrote: > > > >> That said, you may "rm .hgignore," but please don't "hg rm .hgignore." > >> The former will report .hgignore as > >> ! .hgignore > >> ...but a subsequent hg commit will NOT attempt to remove the file. > >> > > > > but an hg update / hg pull -u would regenerate the file, which is > > suboptimal.... > > _______________________________________________ > > tools-discuss mailing list > > [email protected] > > > <holy hack alert> > you could put an 'update' hook in your personal workspace to rm > .hgignore after an update > </holy hack alert> > > yes. hella ugly, but... just saying. :-P
and causes hg status to report: ! .hgignore which is irritating. Why doesn't hgsetup add: [defaults] status = -mard to the user's $HOME/.hgrc file? This would allow me a simple override and I wouldn't have to deal with messing around with .hgignore. And what about project repositories that don't have a .hgignore=* in them? Won't the developer be confused when hg status behaves differently in their workspace after they've done a build? -- Will Fiveash Sun Microsystems Inc. http://opensolaris.org/os/project/kerberos/ _______________________________________________ tools-discuss mailing list [email protected]
