From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Setup non-pushing gerrit instance for glibc.
Date: Thu, 24 Oct 2019 15:39:29 -0400 [thread overview]
Message-ID: <2e93ece9-386b-c587-9355-33a4695a3f02@redhat.com> (raw)
Community,
With the gracious help of Sergio and Simon I have setup a glibc mirror
on a gerrit instance that *cannot* push to sourceware git.
e.g.
git clone ssh://codonell@gnutoolchain-gerrit.osci.io:29418/glibc
< Commit some work >
# First time only, you need a hook to inject commit IDs for tracking.
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 codonell@gnutoolchain-gerrit.osci.io:hooks/commit-msg ${gitdir}/hooks/
git commit --amend --no-edit
###
git push origin HEAD:refs/for/master
The "refs/for/master" is the way to push commits to be applied to master.
---
The purpose of this is to:
* Try out code reviews / CI etc. in gerrit.
- Code review of patches pushed to gerrit is possible.
* Try to setup email based code review in gerrit.
- Currently email is outbound only.
- We are looking at how to make it entirely email based, but tracked
in gerrit.
Enjoy! :-)
--
Cheers,
Carlos.
next reply other threads:[~2019-10-24 19:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:39 Carlos O'Donell [this message]
2019-10-24 21:41 ` Setup non-pushing gerrit instance for glibc Joseph Myers
2019-10-25 0:43 ` Ian Kent
2019-10-25 1:16 ` Jonathan Nieder
2019-10-25 10:21 ` Ian Kent
2019-10-25 1:02 ` Carlos O'Donell
2019-10-25 2:04 ` Sergio Durigan Junior
2019-10-25 3:14 ` Simon Marchi
2019-10-25 4:10 ` Simon Marchi
2019-10-25 14:48 ` Joseph Myers
2019-10-25 15:48 ` Simon Marchi
2019-10-25 16:10 ` Joseph Myers
2019-10-25 16:28 ` Simon Marchi
2019-10-25 1:25 ` Jonathan Nieder
2019-10-25 14:09 ` Florian Weimer
2019-10-25 15:18 ` Joseph Myers
2019-10-25 17:00 ` Sergio Durigan Junior
2019-10-25 20:33 ` Joseph Myers
2019-10-25 21:06 ` Sergio Durigan Junior
2019-10-25 21:13 ` Joseph Myers
2019-10-27 22:12 ` Sergio Durigan Junior
2019-10-28 17:58 ` Joseph Myers
2019-10-28 19:17 ` Jonathan Nieder
2019-10-28 22:59 ` Joseph Myers
2019-10-29 1:21 ` Sergio Durigan Junior
2019-10-25 22:03 ` Jonathan Nieder
2019-10-26 13:53 ` Carlos O'Donell
2019-10-30 18:25 ` Szabolcs Nagy
2019-11-12 18:53 ` Gabriel F. T. Gomes
2019-11-12 19:21 ` Carlos O'Donell
2019-11-12 19:59 ` Florian Weimer
2019-11-12 20:02 ` Jonathan Nieder
2019-11-12 21:10 ` Gabriel F. T. Gomes
2019-11-12 21:13 ` Carlos O'Donell
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=2e93ece9-386b-c587-9355-33a4695a3f02@redhat.com \
--to=carlos@redhat.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).