From: Ian Kent <ikent@redhat.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Setup non-pushing gerrit instance for glibc.
Date: Fri, 25 Oct 2019 18:21:06 +0800 [thread overview]
Message-ID: <33f6c4e78dc50ce38fffbb4a30bc4874f75ff191.camel@redhat.com> (raw)
In-Reply-To: <20191025011641.GA45423@google.com>
On Thu, 2019-10-24 at 18:16 -0700, Jonathan Nieder wrote:
> Hi,
>
> Ian Kent wrote:
>
> > I haven't spent much time with Gerrit but the time I have spent
> > I've found myself thinking Gerrit is designed with the assumption
> > that submissions are "one" patch.
> >
> > I found handling a patch series (which I almost always have when
> > doing changes) rather painful!
>
> Interesting. The Gerrit project itself[1] uses Gerrit and very often
> uses patch series. See [2] for an example.
>
> The section in its documentation on "developing multiple changes in
> parallel"[3] (admittedly poorly named) says a little more about this.
Right, and I have managed to get a couple of multi-patch changes
through the Gerrit review process in the past but I found it very
difficult to find out how to achieve it and I expect the same thing
will happen again next time I need do it.
This likely isn't a problem for people that use Gerrit on a day
to day basis (once familiar with the processes).
So I guess my point is that something specific for new adopters is
needed in the documentation, but of course I could be just plain
thick so maybe it's not worth worrying about, ;)
I also haven't looked at the links you provided so maybe I making
noise about nothing at all, OTOH those likes look a bit familiar
...
>
> Thanks and hope that helps,
> Jonathan
>
> [1] https://gerrit-review.googlesource.com/
> [2] https://gerrit-review.googlesource.com/c/gerrit/+/208641
> [3]
> https://gerrit-review.googlesource.com/Documentation/intro-user.html#multiple-features
next prev parent reply other threads:[~2019-10-25 10:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:39 Setup non-pushing gerrit instance for glibc Carlos O'Donell
2019-10-24 21:41 ` Joseph Myers
2019-10-25 0:43 ` Ian Kent
2019-10-25 1:16 ` Jonathan Nieder
2019-10-25 10:21 ` Ian Kent [this message]
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=33f6c4e78dc50ce38fffbb4a30bc4874f75ff191.camel@redhat.com \
--to=ikent@redhat.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.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).