gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash/server Property.h


From: Chad Musick
Subject: Re: [Gnash-commit] gnash/server Property.h
Date: Fri, 09 Nov 2007 12:41:02 +0900

Might just be me, but I just use:
cvs log -r 'filename' | grep 'author'
if I want to know who has modified a file last. I need to know so rarely
that it's not worth it to me to add the $Id$ line.

On Fri, 2007-11-09 at 03:41 +0100, Markus Gothe wrote:
> I see it's as a much more comfortable way instead of using cvs log/diff.
> 
> Using ccache I don't notice any major issues with rebuilding.
> 
> //Markus
> 
> On 9 Nov 2007, at 02:19, Chad Musick wrote:
> 
> > I'm with Rob -- they also trigger a rebuild after any checkin which
> > touches it. For something like Property.h which gets included in many,
> > many places, the time adds up quickly. I already build and make check
> > before I check in, I don't want to be rebuilding again afterward.
> >
> > Chad
> >
> > On Thu, 2007-11-08 at 16:59 -0800, Rob Savoye wrote:
> >> Markus Gothe wrote:
> >>> CVSROOT:  /sources/gnash
> >>> Module name:      gnash
> >>> Changes by:       Markus Gothe <nihilus>  07/11/09 00:35:01
> >>>
> >>> Modified files:
> >>>   server         : Property.h
> >>>
> >>> Log message:
> >>>   Added $Id:$
> >>
> >>> +/* $Id: Property.h,v 1.14 2007/11/09 00:35:01 nihilus Exp $ */
> >>
> >>   I hate these things, they always break a cvs diff between branches,
> >> and also fill other diffs up with wasted crap. Can you please give  
> >> me a
> >> solid reason (other than just habit) to add these ?
> >>
> >>    - rob -
> >>
> >>
> >> _______________________________________________
> >> Gnash-commit mailing list
> >> address@hidden
> >> http://lists.gnu.org/mailman/listinfo/gnash-commit
> >
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]