This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Setup non-pushing gerrit instance for glibc.
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: "Gabriel F. T. Gomes" <gabriel at inconstante dot net dot br>, libc-alpha <libc-alpha at sourceware dot org>, Sergio Durigan Junior <sergiodj at redhat dot com>
- Date: Tue, 12 Nov 2019 20:59:30 +0100
- Subject: Re: Setup non-pushing gerrit instance for glibc.
- References: <2e93ece9-386b-c587-9355-33a4695a3f02@redhat.com> <20191112155303.2215a667@tereshkova.br.ibm.com> <1f1bbb12-4121-7243-35f7-dd082fc1c4fd@redhat.com>
* Carlos O'Donell:
> For example Gerrit already tells me if patches have merge conflicts, so
> I can ignore those or tell people to rebase.
Gerrit's notion of a rebases and conflicts is a bit unclear to me. I
think it doesn't run the real Git behind the scenes, so it can't know
what kind of conflicts can be resolved by automated merging. For my
patches, I have seen both valid and spurious conflict indicators. In
one case, I could hit Rebase in the web UI and it would automatically
rebase the patch, but it wasn't clear to me why it was needed in that
particular case.
I don't know if any of the other web-based tools handle this better.