Re: gcc breakage

2006-07-11 Thread Laurynas Biveinis
Since I got advised both for and against adding a ChangeLog entry, I'm inclined to leave things as they are for now unless somebody beats me to it. -- Thanks, Laurynas

Re: gcc breakage

2006-07-10 Thread Laurynas Biveinis
You forgot a ChangeLog entry for r115313 | lauras | 2006-07-10 12:44:48 -0700 (Mon, 10 Jul 2006) | 2 lines Fix spaces to tabs in the last commit. I'm not sure. I think that my ChangeLog entry by my previous commit (the

Re: gcc breakage

2006-07-10 Thread Steve Kargl
On Mon, Jul 10, 2006 at 11:24:55PM +0300, Laurynas Biveinis wrote: You forgot a ChangeLog entry for r115313 | lauras | 2006-07-10 12:44:48 -0700 (Mon, 10 Jul 2006) | 2 lines Fix spaces to tabs in the last commit.

Re: gcc breakage

2006-07-10 Thread Daniel Jacobowitz
On Mon, Jul 10, 2006 at 01:34:12PM -0700, Steve Kargl wrote: It's my understanding that every change requires a ChangeLog entry. There is now no consistent record of the difference between 115310 and 115311 without actually looking at svn log fixincludes/Makefile.in. Perhaps, a quick

Re: gcc breakage

2006-07-10 Thread Mike Stump
On Jul 10, 2006, at 1:24 PM, Laurynas Biveinis wrote: Do such changes require ChangeLog entries? For my own beyond trivial fixes that I catch quickly (say, less than 24 hours), normally I just fix them with a `fix typo' type svn log entry. When in doubt, or if you're fixing someone else's