From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: nd <nd@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"Florian Weimer (Code Review)"
<gerrit@gnutoolchain-gerrit.osci.io>
Subject: Re: [review] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25...
Date: Mon, 11 Nov 2019 15:09:54 +0000 [thread overview]
Message-ID: <566ecda0-be75-7f46-4abf-c68cceb0640f@arm.com> (raw)
In-Reply-To: <87bltpm0wd.fsf@oldenburg2.str.redhat.com>
On 06/11/2019 16:21, Florian Weimer wrote:
> * Szabolcs Nagy:
>
>> On 03/11/2019 17:11, Florian Weimer (Code Review) wrote:
>>> Change URL: https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/489
>>
>> i can't login to gerrit. is there something special i need to do?
>
> You need to create an account. I can't seem to send a direct link to
> the page, but there is a Register link on the sign in page.
that's what i expected but it does not work for me.
and if i try to register again it says email already exist,
but i've never got a verification mail (i tried the resend
link several times).
creating another account with different email didn't work either
(first i missed the timeout: i got the mail 10 minutes after
registration and it said the verification link expires after
15 min.. then after a few tries i managed to follow the verification
link but it just says 'Forbidden' and all later site access just
kept saying forbidden even though i never asked the site to
remember my login.. i had to clear all the site related cookies
to be able to visit the registration site again)
i'm a bit lost how to debug this, i guess i'll stay away from
gerrit until there is a solution that works.
>
> Afterwards, someone needs to add you to the glibc maintainers group, so
> that you can give +2s.
next prev parent reply other threads:[~2019-11-11 15:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 17:11 [review] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25 Florian Weimer (Code Review)
2019-11-06 16:12 ` Szabolcs Nagy
2019-11-06 16:21 ` Florian Weimer
2019-11-11 15:09 ` Szabolcs Nagy [this message]
2019-11-11 15:12 ` Florian Weimer
2019-11-11 21:41 ` Sergio Durigan Junior
2019-11-12 10:22 ` Szabolcs Nagy
2019-11-12 10:35 ` Florian Weimer
2019-11-09 11:44 ` [review v2] " Florian Weimer (Code Review)
2019-11-12 10:40 ` Szabolcs Nagy (Code Review)
2019-11-12 11:47 ` [review v3] " Florian Weimer (Code Review)
2019-11-12 17:29 ` Joseph Myers
2019-11-12 17:42 ` Sandra Loosemore
2019-11-12 18:04 ` Joseph Myers
2019-11-12 18:42 ` Florian Weimer
2019-11-12 20:59 ` Sandra Loosemore
2019-11-13 5:47 ` Florian Weimer
2019-11-13 16:04 ` Sandra Loosemore
2019-11-13 16:25 ` Florian Weimer
2019-11-13 16:06 ` Jeff Law
2019-11-12 22:14 ` Carlos O'Donell
2019-11-12 22:18 ` Florian Weimer
2019-11-12 22:24 ` Carlos O'Donell
2019-11-12 22:26 ` Florian Weimer
2019-11-12 22:39 ` Joseph Myers
2019-11-13 6:18 ` Florian Weimer
2019-11-13 16:05 ` Jeff Law
2019-11-12 23:12 ` Sandra Loosemore
2019-11-12 23:15 ` Joseph Myers
2019-11-12 12:53 ` Szabolcs Nagy (Code Review)
2019-11-12 13:00 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-12 13:00 ` Sourceware to Gerrit sync (Code Review)
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566ecda0-be75-7f46-4abf-c68cceb0640f@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=fweimer@redhat.com \
--cc=gerrit@gnutoolchain-gerrit.osci.io \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).