On Thu, 2009-02-19 at 06:02 +0000, TK Soh wrote: > On Thu, Feb 19, 2009 at 5:53 AM, Steve Borho <[email protected]> wrote: > > On Thu, 2009-02-19 at 00:23 -0500, Doug Philips wrote: > >> On or about Wednesday, February 18, 2009, at 01:33AM, Steve Borho indited: > >> >I prefer for unknowns to be shown in commit be default. Forgetting to > >> >add new files is just too common of a problem. > >> > > >> >With the new hgignore dialog, I'm hoping it will be easier for people to > >> >maintain decent ignore patterns so any unknowns that do show up are > >> >meaningful. > >> > >> Well, my problem is that hgignore won't help. > >> I have lots of noise files (t1.py, t2.py, foo.py) floating around in > >> my tree as I am trying out things too tedious to retype into the > >> python top level, but really of no interest to anyone else but me. > >> > >> I suppose I could have a personal naming scheme: ignore1.py, > >> ignore2.py, but I am really loathe to have a pattern in .hgignore that > >> would automatically discount any .py file no matter how obscure. > >> For now I will live with the unknowns in the commit dialog. :) > > > > Would an undocumented [tortoisehg] option for this be sufficient for > > 0.7? > > What kind of option?
Something like 'commit.showunknown' that defaults to True if not configured. The name doesn't matter that much. We can add it to thgconfig later if we need to. -- Steve ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
