This is the mail archive of the libc-alpha@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]

Re: How to submit a patch set?


Thanks for the note. I will send the patches sometime in the next few
days. I will ask that one of the glibc regulars handle Bugzilla if
necessary. I have almost exhausted the energy that I have to devote
to this. :-)

Thanks,

Arnold

"Carlos O'Donell" <carlos@redhat.com> wrote:

> On 12/03/2017 12:35 PM, arnold@skeeve.com wrote:
> > I went through all the changes between the glibc regex and the gawk
> > regex and have put them together as 17 separate patches.  What is the
> > best way to submit them for inclusion into glibc?  I have signed
> > paperwork for GLIBC so that's not an issue.
> > 
> > I can send one email with 17 attachments, or 17 separate mails, or attach
> > a tarball, or ...
> > 
> > Please let me know.
> > 
> > Please reply directly; I am not on this mailing list.
>
> Thank you for all of your effort!
>
> Please send 17 distinct emails so we can follow up on each.
> Start with a 0 email which describes the patchset.
>
> In general everyone follows this:
> https://sourceware.org/glibc/wiki/Contribution%20checklist
>
> I've moved this conversation over to libc-alpha where the
> developer discuss these issues.
>
> Cheers,
> Carlos.


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