We need to find out if per file comments are possible, but just not supported by the tool.
Matt On 7/25/06, Satish Balay <balay at mcs.anl.gov> wrote: > > On Tue, 25 Jul 2006, Barry Smith wrote: > > > On Tue, 25 Jul 2006, Satish Balay wrote: > > > > > Yes - not having file comments makes it more difficult to go back in > > > file history. > > > > > > But one way to look at it is - for some of these senarios - it meanas > > > multiple changesets should be created [with the correct grouping of > > > changes] instead of the atempted single changeset. > > > > Yes, the problem with this is that there is no decent way of > > making multiple change-sets. > > - quit emacs without typing in any comments [so no commit is done] > - 'hg status' to get the list of modified files > - hg commit file1 file2 [ to make the appropriate changeset] > > I use 'hg ct' though.. > > > If I could just edit out the files > > I did not want when doing the comment for a commit it would make > > life a MILLION times better (could that be added?). > > I'll check on this on the mercurial list.. > > Satish > > > > > Barry > > > > > > > > And perhaps some comments can actually go into the code. > > > > > > Satish > > > > > > On Tue, 25 Jul 2006, Barry Smith wrote: > > > > > > > > > > > Not having file by file comments for changesets is > > > > starting to annoy me. > > > > > > > > Barry > > > > > > > > > > > > > > > > > > > > -- "Failure has a thousand explanations. Success doesn't need one" -- Sir Alec Guiness -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20060725/6750a8b3/attachment.html>