This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Minor patch(es)
On Mon, Aug 23, 2010 at 2:53 PM, Linas Vepstas <linasvepstas@gmail.com> wrote:
> Hi,
>
> I've been slowly porting glibc to a new architecture (a cpu from Qualcomm)
> and have a handful of "minor" patches, non-architecture-specific ÂWhat's the
> best way to submit these? Here? or via a bugzilla bug report? ÂFor example,
> see the below: Â(I'm submitting this in lkml signed-off-by style; I've
> no clue if
> this is appropriate)
>
>
> The old glibc used to have uname.c in ./sysdeps/generic/uname.c
> and so the configure check for "$uname" = "sysdeps/generic" made
> sense. ÂHowever, the current glibc has it in ./posix/uname.c and
> the search returns "sysdeps/unix" for this case. ÂA cross-compile
> build fails without this fix.
>
> Signed-off-by: Linas Vepstas <linasvepstas@gmail.com>
Hi Linas,
You're missing a GNU style ChangeLog. You can find directions on
writing one on the following wiki:
http://sourceware.org/glibc/wiki/Contribution_checklist
Patches which apply against ports/ go to the libc-ports mailing list.
This particular patch should go to libc-alpha (once you have a
ChangeLog entry) since it appears to be non-ports.
Since this patch is insignificant you won't need FSF copyright
assignment. If you need to add new files or do significant changes to
existing files for this new architecture you'll need to gain FSF
copyright assignment.
You can also open bug reports, and in-fact I recommend that. Your
patch is less likely to be missed that way.
Ryan