On Wed, Jan 14, 2009 at 2:10 PM, Steve Borho <[email protected]> wrote: > On Tue, Jan 13, 2009 at 10:55 PM, TK Soh <[email protected]> wrote: >> >> > Having 'unknowns' visible at startup should be a sticky option. You >> > risk >> >> We want to avoid making sticky option selectively. If we are going to >> make 'unknown' sticky, then all the other options should be too. >> >> > forgetting to add/commit new files without it. You may also miss >> > copies/renames. >> >> I am not sure if the risk is a valid one. An add/copy/rename/.... >> action is a result of an intention. If the user wants to add, then >> they will try look for the file in the list, and learn why it's not >> there. > > The most common build breakage you see when working with teams of any size > is forgetting to check in new files. "Everything built for me, why doesn't > it work for you?". People very easily forget they added a new file when it > comes time to commit. I'm almost always surprised when I see unknowns show > up at commit time. > > At the very least, this needs to be an option.
Sure. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
