On 4/20/09, Zarel <[email protected]> wrote: > 2009/4/19 Giel van Schijndel <[email protected]>: > > > Please include the full changelog in your commit message. There's no > > size limit on it... I don't like dependencies like this on external > > sources. > > > This isn't the first time this has come up. Let's agree on a solution > right here and now, so we don't have to go through this every time I > commit Rebalance. > > Per and I agreed on this solution: considering I change everything so > many times, it's simpler to just provide a full changelog from 2.1 > when Rebalance is finished. Otherwise, it's too much information. I > change minor values once, then change them back when they don't work, > etc, etc. > > I will name every single change I made when Rebalance is finished. > Doing it each commit simply requires more time than even making the > changes and playtesting them over and over. The summary of major > changes and the website with detailed changes is enough. It won't go > down before my full changelog when Rebalance is finished, anyway. And > the data is separate enough that we can revert all of it while leaving > the rest of the code untouched. > > Everyone agree? >
Are you saying you commit the changes first, then write your changelog at your site? If not, a simple copy & paste from that would be good enough for the most part. I rather see a '+' | '-' table generated, so at a quick glance, we can all tell if you nerfed something, or made something stronger. The main point is, when you say something like "VTOLs partially fixed. " and don't go into details on the how & why, it gets a bit confusing to those that don't live in CSV hell ;), and they must do a diff to see what you have done. _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
