From: Roland McGrath <roland@hack.frob.com>
To: overseers@sourceware.org
Cc: "H. J. Lu" <hongjiu.lu@intel.com>,
Joseph Myers <joseph@codesourcery.com>,
Carlos O'Donell <carlos@codesourcery.com>
Subject: add hjl to glibc group
Date: Thu, 15 Mar 2012 23:44:00 -0000 [thread overview]
Message-ID: <20120315234445.174292C058@topped-with-meat.com> (raw)
Please add hjl to the glibc group so he can use git push.
HJ, we'll of course expect you to follow the conventions stated on the wiki
and take great care in any commits, and then to commit your own changes
only after explicit approval.
You're free (and encouraged) to create any hjl/* branches you like,
provided everything therein has clear FSF copyright assignment in place.
It's the most convenient way for other glibc developers to look at your
code before it's approved for merge. If you put individual changes on
their own topic branches and mention the branch name when proposing a
change, then approvers can just use "git merge" rather than actually
applying patches to get a change onto the trunk.
Thanks,
Roland
next reply other threads:[~2012-03-15 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 23:44 Roland McGrath [this message]
2012-03-16 2:39 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120315234445.174292C058@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=carlos@codesourcery.com \
--cc=hongjiu.lu@intel.com \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).