This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
FYI: Status of gdb usage of gerrit
- From: Carlos O'Donell <carlos at redhat dot com>
- To: libc-alpha <libc-alpha at sourceware dot org>
- Date: Fri, 22 Nov 2019 21:56:58 -0500
- Subject: FYI: Status of gdb usage of gerrit
The summary is that gdb will no longer use gerrit because of:
* lack of cover letters
* lack of mail threading for patch series
Please read this for the status update:
https://sourceware.org/ml/gdb-patches/2019-11/msg00749.html
For me neither of these items are as important to me as:
* accurate patch tracking
* UI for side-by-side review and commenting
* patch version tracking with patch IDs (changeset IDs)
* detailed comment tracking to ensure that all comments are
reviewed for all versions
* ability to use git to fetch a patch and test it.
You can work around the lack of a cover letter by using
an empty commit with a message.
You can work around the lack of mail threading for patch
series by using a subject prefix that's numbered like
a series e.g. "nodelete 1/12: Introduce
DL_LOOKUP_FOR_RELOCATE flag for _dl_lookup_symbol_x"
Then you can go through your mail looking for nodelete
1-12.
I'm happy to hear any feedback those of you have about
working with gerrit.
--
Cheers,
Carlos.