no file comments for hg

Barry Smith bsmith at mcs.anl.gov
Tue Jul 25 20:59:48 CDT 2006


   Satish,

    Your proposed solution is ridiculously cumbersome; no sane person
would put up with that nonsense.

   If the authors of the ct would get their heads out of their
asses and update it to Qt4 (which is like, what, a year old) instead
of the outdated Qt3 maybe people who use updated software could use it.

    Barry


On Tue, 25 Jul 2006, Satish Balay 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>




More information about the petsc-dev mailing list