From: Florian Weimer <fw@deneb.enyo.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: How to keep Reviewed-by lines in git commits with gerrit.
Date: Tue, 12 Nov 2019 21:48:00 +0100 [thread overview]
Message-ID: <87o8xges8v.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20191112195939.GA25693@google.com> (Jonathan Nieder's message of "Tue, 12 Nov 2019 11:59:39 -0800")
* Jonathan Nieder:
> There's a Gerrit hackathon[3] ongoing as we speak. If you have any
> questions you'd like me to relay to Gerrit devs or if you'd like to
> meet up on IRC or video chat, let me know.
I've got a question: Is there a way to produce a direct link to the
signup page?
Our instance generates a signup link like this:
<https://gnutoolchain-gerrit.osci.io:8877/auth/realms/gerrit/login-actions/registration?client_id=gerrit&tab_id=h8iVt3Ny_2s>
But as you can see, it won't work in another browser session.
The reason I'm asking is that it would be nice to put a link to the
signup page into the documentation, so that would-be contributors can
just click on the link and create their account.
Maybe that's specific to the Keycloak integration we have, though.
next prev parent reply other threads:[~2019-11-12 20:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 17:35 How to keep Reviewed-by lines in git commits with gerrit Carlos O'Donell
2019-11-12 17:40 ` Joseph Myers
2019-11-12 19:05 ` Carlos O'Donell
2019-11-12 22:26 ` Joseph Myers
2019-11-12 22:35 ` Florian Weimer
2019-11-12 22:47 ` Joseph Myers
2019-11-12 19:07 ` Florian Weimer
2019-11-12 19:30 ` Carlos O'Donell
2019-11-12 19:39 ` Florian Weimer
2019-11-12 19:59 ` Jonathan Nieder
2019-11-12 20:02 ` Florian Weimer
2019-11-12 20:08 ` Jonathan Nieder
2019-11-12 20:14 ` Florian Weimer
2019-11-12 20:42 ` Carlos O'Donell
2019-11-12 20:56 ` Florian Weimer
2019-11-12 20:48 ` Florian Weimer [this message]
2019-11-12 21:04 ` Carlos O'Donell
2019-11-12 21:10 ` Florian Weimer
2019-11-12 22:11 ` Carlos O'Donell
2019-11-13 13:39 ` Siddhesh Poyarekar
2019-11-13 17:20 ` Tulio Magno Quites Machado Filho
2019-11-13 17:33 ` Florian Weimer
2019-11-13 3:29 ` Carlos O'Donell
2019-11-13 18:16 ` Joseph Myers
2019-11-13 18:18 ` Florian Weimer
2019-11-13 21:38 ` Jonathan Nieder
2019-11-13 23:31 ` Jonathan Nieder
2019-11-12 20:40 ` Carlos O'Donell
2019-11-12 20:57 ` Florian Weimer
2019-11-12 21:09 ` Carlos O'Donell
2019-11-12 21:19 ` Florian Weimer
2019-11-12 21:20 ` Carlos O'Donell
2019-11-12 21:21 ` Florian Weimer
2019-11-12 21:22 ` Carlos O'Donell
2019-11-12 21:23 ` 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
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=87o8xges8v.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@redhat.com \
--cc=jrnieder@gmail.com \
--cc=libc-alpha@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).