[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[patches] Re: [commits] r3856 - in /branches/libdfp/libc/dfp: ./ bits/ sysdeps/ sysdeps/dfp/ sysdeps/dfp/math/ sysdeps/dfp/math/bits/ sysdeps/dfp/st...
- To: Peter Eberlein <eberlein@xxxxxxxxxx>
- Subject: [patches] Re: [commits] r3856 - in /branches/libdfp/libc/dfp: ./ bits/ sysdeps/ sysdeps/dfp/ sysdeps/dfp/math/ sysdeps/dfp/math/bits/ sysdeps/dfp/st...
- From: Jim Blandy <jimb@xxxxxxxxxxxxxxxx>
- Date: Fri, 19 Oct 2007 14:15:08 -0700
I'm glad to see the DFP work going onto branches/libdfp.
Congratulations!
By the way --- when you commit, you should also post to this list.
Generally, you should post the patch, with the ChangeLog entry at top,
as in:
http://www.eglibc.org/archives/patches/msg00362.html
The patch should not include changes to generated files like
'configure'.
In this case, posting the patch probably isn't too helpful, but you
should go ahead and post explaining what you've done.
On the trunk, changes specific to EGLIBC are logged in
ChangeLog.eglibc, at the top of each source tree, and in the
Subversion logs. Whether you follow that rule on your branch is up to
you, but I'd encourage you to do so, to help other folks follow what's
going on. When we eventually merge to trunk, we'll probably just put
a summary entry in the trunk's ChangeLog.eglibc.