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]

Re: How to push patches to glibc

From: Carlos O'Donell <carlos at redhat dot com>
To: Feng Xue <fxue at os dot amperecomputing dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
Date: Mon, 7 Jan 2019 22:07:15 -0500
Subject: Re: How to push patches to glibc
References: <BL0PR01MB45930D2120E9CFE47CE2FC2DF78A0@BL0PR01MB4593.prod.exchangelabs.com>

On 1/7/19 9:47 PM, Feng Xue wrote:
> I've made some patches that have been reviewed and accepted by some
> maintainers. Now I want to upstream them, but I think I need an
> account with allowed access to the master repo, as something
> mentioned in the wiki:
> 
> git clone ssh://"USER@sourceware.org"/git/glibc.git
> 
> How can I apply this kind of account? Or since we have signed
> copyright assignement with the FSF, it possible to add access to the
> email account listed in the copyright assignment?

The information is listed here:

"Becoming a maintainer (developer)"
https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29

The first step is to have a signed copyright assignment with the FSF.

If you have any questions, please don't hesitate to ask.

-- 
Cheers,
Carlos.

References:
- How to push patches to glibc
  - From: Feng Xue

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