[Gc] libatomic_ops: Lastest commits

Boehm, Hans hans.boehm at hp.com
Thu Sep 10 10:56:20 PDT 2009


I agree it's not worth fixing.  So long as the ChangeLog entry is in the ChangeLog file, and we do the right thing in the future, we should be fine.  

Hans 

> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com 
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Ivan Maidanski
> Sent: Thursday, September 10, 2009 10:50 AM
> To: gc at napali.hpl.hp.com
> Subject: Re[2]: [Gc] libatomic_ops: Lastest commits
> 
> Hi!
> 
> "Boehm, Hans" <hans.boehm at hp.com> wrote:
> > I take it that means you have sufficient permissions to 
> check things in?
> > 
> > I was trying to check and adjust your permissions, but 
> something wasn't working correctly, and the browser hung. 
> 
> Yes, it works correctly. The only thing is that in my first 
> commit I've set the log message to "diff108_cvs" instead of 
> the new changelog entries - You can fix it (using admin 
> command) but I don't think it's really worth fixing. You 
> could see this in:
> http://bdwgc.cvs.sourceforge.net/viewvc/bdwgc/bdwgc/libatomic_
> ops-1.2/src/atomic_ops/sysdeps/gcc/x86_64.h?view=log
> http://bdwgc.cvs.sourceforge.net/viewvc/bdwgc/bdwgc/libatomic_
> ops-1.2/src/atomic_ops/sysdeps/msftc/x86_64.h?view=log
> http://bdwgc.cvs.sourceforge.net/viewvc/bdwgc/bdwgc/libatomic_
> ops-1.2/src/atomic_ops/sysdeps/standard_ao_double_t.h?view=log
> 
> > 
> > Hans
> > 
> > > Hi!
> > > 
> > > If no objections, I've committed all the pending 
> libatomic patches - 
> > > diff108_cvs, diff109_cvs, diff110, ivmai122.diff, 
> ivmai123.diff (the 
> > > last one dated Aug 28).
> 
> Bye.
> 
> _______________________________________________
> Gc mailing list
> Gc at linux.hpl.hp.com
> http://www.hpl.hp.com/hosted/linux/mail-archives/gc/
> 


More information about the Gc mailing list