> I have been doing putbacks to Solars ON-gate since the early 90s, so I > am very used to the Teamware way of doing things. I have read all the > Mercurial docs (that I could find), but I'm still uncertain about the > correct way to enter the comments which will be recorded with my push > and which we are used to seeing in the gate notification mail inside > Sun. > > Is the following an acceptable approach? > > Do as many "commits" as you like in your repository clone, with whatever > comments are useful to you. These are temporary. > > Then, when it's time to push (assuming hg pbchk is clean and > RTI is approved), do a final 'hg recommit' and enter the *real* > comments. Something like "hg recommit -l ~/comments.txt" > > where ~/comments.txt contains, for example, > > --- > FWARC 2008/229 Virtual IO DR Domain Service > 6651197 Add support for LDoms Virtual I/O Dynamic Reconfiguration (VIO DR) > ---
Mostly correct, though if you enter useful comments all along the way, and don't use the "-l" option to "hg recommit," cadmium will initialize a buffer with the collected comments from all of the changesets it's collapsing, and you can edit it in place. > Another question: From what I have been able to tell from experiment, a > commit message (or comment) applies to all the files which are currently > uncommited and not any individual file. If I'm fixing several bugs in a > changeset, have I lost the ability to enter file-specific comments? Right, a commit message applies to the whole changeset. The changeset comments will get you to a collected set of bug reports, where you should correlate bugs to files and diffs. --Mark > > Thanks, > > Jim > > _______________________________________________ > scm-migration-dev mailing list > scm-migration-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev >
