On Wed, Jan 14, 2009 at 1:18 PM, TK Soh <[email protected]> wrote: > On Wed, Jan 14, 2009 at 5:14 AM, Abdul Halim <[email protected]> wrote: >> On Wed, Jan 14, 2009 at 12:55 PM, TK Soh <[email protected]> wrote: >> >>> >>>> should it unshelve a file after it has been committed? this would be >>>> more >>>> record-like >>> >>> I don't think so. Record works by shelving the changes before >>> committing [the remaining ones], so it must unshelve after the commit. >>> In our case, shelve is initiated by user, so unshelve should be so >>> too. >>> >> >> I disagree on this. I may tend to forget the files after shelving it. >> This is especially true >> if there is large files to be commit and large number of files shelved -> >> due to urgent update, but I still want a separate history of what I did. >> I might be doing consecutive records/shelves at one go. >> Messy it seems but sometimes I have to do urgent patches. > > No offense, but the problem appears to be in your work > habit/environment. We can't make the tool to help you remember. You > need to be responsible for your own actions, i.e. unshelve those you > shelve. >
Neh.. It is not the habit.. It is the environment. Especially, when the customer is beside you breathing down your neck. Guess I have to stick to Qct then. ------------------------------------------------------------------------------ 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
