From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Makeconfig: Use $(error ...) to output error message
Date: Thu, 30 Apr 2020 23:31:20 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2004302327010.851719@eddie.linux-mips.org> (raw)
In-Reply-To: <6fbf8a68-a6b3-ac8e-4ed8-94bae46b2e7d@efficios.com>
Hi Simon,
> Thanks, could you please push it for me? I don't have write access to the
> glibc repo (and don't plan to make enough contributions to justify it).
FTR I don't think you need any additional credentials to push to any of
the repos hosted at sourceware as long as you have an account there, and
obviously you do.
Maciej
next prev parent reply other threads:[~2020-04-30 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 22:20 Simon Marchi
2020-04-28 23:33 ` Joseph Myers
2020-04-28 23:48 ` Simon Marchi
2020-04-29 9:25 ` Florian Weimer
2020-04-29 13:51 ` Simon Marchi
2020-04-30 22:31 ` Maciej W. Rozycki [this message]
2020-05-01 0:22 ` Simon Marchi
2020-05-01 16:20 ` Florian Weimer
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.LFD.2.21.2004302327010.851719@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=simon.marchi@efficios.com \
/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).