From: Joseph Myers <joseph@codesourcery.com>
To: Andrew Senkevich <andrew.n.senkevich@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>, <overseers@sourceware.org>
Subject: Re: [PATCH 3/N] [x86_64] Vectorized math functions
Date: Sun, 30 Nov 2014 19:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1411271419470.20972@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMXFM3u9mp+XuAZz4G7L2j=74JpQwxO2M9oSEQ3krOGsDGvpaQ@mail.gmail.com>
On Thu, 27 Nov 2014, Andrew Senkevich wrote:
> 2014-11-26 19:53 GMT+03:00 Joseph Myers <joseph@codesourcery.com>:
> > Again, it would be helpful if you had a git branch with the latest rebased
> > version of this patch series, updated each time a patch changed, so we
> > could see where this is heading. See
> > <https://sourceware.org/glibc/wiki/GlibcGit>: branches under the
> > <username>/ namespace can be freely created and deleted.
>
> Ok, I have applied for sourceware.org account and point you as person
> who approved request (in this form -
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi).
> Will wait for account.
The copyright assignment paperwork still needs to be completed before you
can get write access. I don't see you in copyright.list.
--
Joseph S. Myers
joseph@codesourcery.com
next parent reply other threads:[~2014-11-27 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMXFM3ueRnbLVeTh9BrU27hwwdU=WEsrN7iC0o=c6d53mbsz6A@mail.gmail.com>
[not found] ` <alpine.DEB.2.10.1411211757030.2475@digraph.polyomino.org.uk>
[not found] ` <CAMXFM3vbyrZ-iUR5Kd7L8CMakpn+ObdTeKTYkfLj+Uzt3v5GEQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.10.1411261643500.854@digraph.polyomino.org.uk>
[not found] ` <CAMXFM3u9mp+XuAZz4G7L2j=74JpQwxO2M9oSEQ3krOGsDGvpaQ@mail.gmail.com>
2014-11-30 19:28 ` Joseph Myers [this message]
2014-12-01 20:27 ` Christopher Faylor
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=alpine.DEB.2.10.1411271419470.20972@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=andrew.n.senkevich@gmail.com \
--cc=libc-alpha@sourceware.org \
--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).