On Tuesday, 01 March 2005, at 06:44:19 (+0100), Cristalle Azundris Sabon wrote:
> Not to mention that in my last checkout, the .spec files did not > reflect these changes. Can we establish the rule that (collective) > you DON'T change the version number UNLESS you also fix the spec? > Thanks. As I was going to tell that other guy (Richard?), I haven't updated the spec files because I'm still trying to understand the logic behind changing 18 packages to fix 3. The spec files already had the "snapshot" functionality in them, so I just reverted the change on the 15 packages that didn't need it. Some discussion of this BEFORE the change was made would've been nice. But then, I guess that's not the way things happen around here. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "As your attorney, it is my duty to inform you that it is not important that you understand what I'm doing or why you're paying me so much money. What's important is that you continue to do so." -- Hunter S. Thompson's Attorney ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
