[gmx-users] where is the gromacs 4.0.6/7 revision list?
Mark.Abraham at anu.edu.au
Sun Dec 13 03:08:08 CET 2009
chris.neale at utoronto.ca wrote:
> Thanks again Mark,
> are you able to provide a bug number for "Fixed bug with pull groups
> using weights in parallel" so that I can figure out exactly what the
> problem was?
I can't. The existing links are where the committer mentioned a bug
number, or Justin and I knew the numbers already. Searching bugzilla is
your best bet.
> Separately, it seems like a decent idea to automate the production of
> this list and its update on the website whenever a new version is
> released... if that's even possible. I know that the tools section of
> the gromacs manual is autogenerated from the tool -h output, so that
> might be one route to make this happen.
Agreed - automation would be welcome. Making sure committers note
bugzilla numbers would be very useful start. Secondarily, they should
consider a git commit that's intelligible to someone who hasn't read the
code diff. The best automatic solution I could suggest would be a perl
script to postprocess a git log. That'd still have to go up on a wiki
after editing by hand, though.
>> Subject: Re: [gmx-users] where is the gromacs 4.0.6/7 revision list?
>> To: Discussion list for GROMACS users <gmx-users at gromacs.org>
>> Message-ID: <4B243D38.1000606 at anu.edu.au>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>> chris.neale at utoronto.ca wrote:
>>> Thanks for taking the time Mark, this is quite useful. Especially "Bug
>>> 354: switching from Berendsen to V-rescale doesn't work if -nosum is
>>> used" for those of us who don't follow the list every day.
>> Yes, I thought that bug might be of more than minor interest to some
>> I've done an extensive update to the 4.0.7 revision list here
>> based on the git commit comments. Git made life really easy to get a
>> list of the relevant commits with a diff nearby, so where the comment
>> was cryptic and I either knew about the issue or could infer from the
>> code changes, I clarified and expanded.
>> People who've committed to release-4-0-patches this year should
>> definitely cast their eye over the list to check my work.
>> Justin, I wasn't sure to which commit your previous "constraints =
>> h-angles" referred, so I left it at the bottom of the list. Please edit
>>> -- original messagwe --
>>> I started a 4.0.7 revisions list there and noted the issues that came to
>>> mind. The canonical source for such a list should be the git commits
>>> but these are often cryptic and need re-writing for a revisions list
>>> useful to non-developers. When I have some more time I'll put more
>>> revisions up, but others should make an effort for things they've
More information about the gromacs.org_gmx-users