This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

How to upstream glibc patch?


Hi,
I've already upstreamed some patches to kernel and uboot, but glibc's patch
upstreaming seems different.
I know here is the wiki page
https://sourceware.org/glibc/wiki/Contribution%20checklist
but something is still unclear for me, especially the changelog.

for example I do like this:
git format-patch -1
../gcc/contrib/mklog my-patch-file
then I get:

Unknown ChangeLog:

2018-06-08  Hongbo Zhang  <hongbo.zhang@linaro.org>

* sysdeps/aarch64/multiarch/memcpy.c (libc_ifunc):
* sysdeps/aarch64/multiarch/memmove.c (libc_ifunc):
* sysdeps/aarch64/multiarch/memset.c (libc_ifunc):
* sysdeps/unix/sysv/linux/aarch64/cpu-features.c:
* sysdeps/unix/sysv/linux/aarch64/cpu-features.h (IS_PHECDA):

then what is the next?
I copy these texts into my patch file as a part of commit message?
I see it is blank after each colon in the changlog generated above, should
I add some message manually? or leaving them blank is acceptable?


Thanks.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]