On 08.01.2010 03:08, Steve Borho wrote: > On Wed, Jan 6, 2010 at 7:50 PM, Michael Jay Lippert > <[email protected]> wrote: >> When I updated to the latest version of TortoiseHg (0.9.1) I noticed that >> the checkbox next to !:deleted seemed to have been removed, I assumed by >> accident. >> >> I just filed this bug >> Issue 847: Commit dialog missing deleted checkbox under View 'MAR?!' >> http://bitbucket.org/tortoisehg/stable/issue/847/commit-dialog-missing-deleted-checkbox-under-view >> >> where I found out that the checkbox had actually been removed by design. >> >> As I said in my final comment in that bug: >> >> I do however disagree with the change. I find it very valuable to only >> display 1 type of file at a time while looking over the modifications that >> have happened. In general this means I want to see only the deleted files, >> or only the unknown files. >> >> I've been trying to use mercurial at work where we use ClearCase (yech) but >> this means that I have a lot of changes to the repository at one time, and >> it is very useful to isolate the type of files displayed. >> >> Steve suggested that I start a discussion on the mailing list about >> restoring that checkbox. >> >> I'm curious to hear why some people thought it would be better not to let >> users hide the deleted files from the list of all changes. I realize that it >> is important to know that some files in the repository have been deleted >> without being removed, but all the other categories of modified files are >> also important and yet the options to hide them still exist. Mostly I really >> like the option to look at any particular set w/o the others showing. > > FWIW, I've also encountered a work-flow that could also benefit from a > deleted file toggle. > > Recently I've been using TortoiseHg as a front-end to a perforce > server, by way of the new perfarce extension. Perforce is one of the > few remaining VCS systems that requires you to open files for edit > before modifying them. This is a side-effect of the way they manage > mappings of files from the server to the client. > > Perforce also allows you to check in files that are marked to always > be writeable, and people abuse this feature in the worst sorts of > ways... checking in build remnants that are intended to be overwritten > when you build files yourself. > > When you import these repositories into Mercurial and work in them, > these build remnant files are usually modified (built) or missing > (cleaned). I've been simply reverting them all before doing commits, > but it would be nice to be able to toggle off their display. > > That's my 2p.
I was the one who removed the capability to hide deleted files. I did this intentionally, because newbies occasionally unintentionally delete tracked files without intending to remove them in mercurial and it is very easy to uncheck that box, hide it and forget about having done so (resulting in nicely hiding your own stupidity, since the red exclamation mark entries are then gone). I couldn't think of any halfway sane use case for hiding deleted files, so I removed that checkbox when I ui-refactored these. Since I don't care that much about such things in mercurial anymore, feel free to readd it. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
