This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Commit messages and the move to git
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, Segher Boessenkool <segher at kernel dot crashing dot org>, Eric Raymond <esr at thyrsus dot com>, Jeff Law <law at redhat dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 19 Dec 2019 14:29:46 +0000
- Subject: Re: Commit messages and the move to git
- Ironport-sdr: I9xib+UDLNrR8ZEYs6IIDeXvv8cMBlZvzVDTE4L7+aNI5edZKe+nzA6i0U6mUCWJjc+EYCsveS 0h1+LI5v3/Ius/T9sbq4MAg9QACeXjn27tuxfFb6OxgOR3MCs67Pb8LS0ZmHgqyRGL63Kr4YyY +9OXQwfUmH24EcF6I65GHwcjlFTzDTkwli05Tg+niWYzGPpG3auEhlbnjymSOzyPPHjbg3ojHu 8HUXLa7/2lMbnt0FWZGWZWuCSNcnoqWuliSIdGntSpPXllFusYbg9mVhb/5bG7xFdm62D+WU9F PyQ=
- Ironport-sdr: rkd/hxmquPCWRGDxQ1vehOu1Yc6AyyRGFSMji6YmdyS6zMVpNHRJ6UgCkm+3d/qR+yIlLBvuNd yLgtFT8qEaepgQAsrQd3vYEY/eBNQYauvtk4YW9rbsPSPk4DL4FdOI5HnqqfYyHr+3euExp7NS /Y7QdlEvWpLfE6WHBWVJS5VLiyQRsyPLWh6jkA8pp9Kc7wcMngyrTf66n9KwmJPqjA+FqB5ukN sh+bGctaOLrcoTJMyzotILrGm8wruUg6LSRqGepT054f4zYpo97Fho9OHTRFccWywj9PiVkOSC GZ8=
- References: <f54f97d0-ed07-bfd6-ce1d-1f5e498f9697@arm.com> <e6f9205c-1f9c-2d50-67b7-611f45bf6a25@redhat.com> <20191107142727.GA72444@thyrsus.com> <a5e2428c-60d5-3157-6b5f-662cfa76767b@arm.com> <20191109060151.GA82270@thyrsus.com> <78a57894-74f2-94d5-65a1-3ce2bd934f32@arm.com> <20191118155549.GH16031@gate.crashing.org> <fb6aa5da-9bc7-1fb5-4dee-efdcdf849a46@arm.com> <20191118171115.GI16031@gate.crashing.org> <ac635c47-884c-3832-193b-d45ce9336bca@arm.com> <alpine.DEB.2.21.1912182337150.12074@digraph.polyomino.org.uk> <alpine.DEB.2.21.1912182359470.12074@digraph.polyomino.org.uk> <CAH6eHdT+g6k-zEDzX6OGz-7xT7OjHNbvGPOPBi8XW+xjoOoF6A@mail.gmail.com> <6e226ca8-f0f1-f4a2-80dc-f19e5dec327d@arm.com>
On Thu, 19 Dec 2019, Richard Earnshaw (lists) wrote:
> Best of all would be a pull request on
> https://gitlab.com/esr/gcc-conversion/tree/master to update bugdb.py directly.
Note if doing that, it helps to check "Allow commits from members who can
merge to the target branch." when creating the merge request (that allows
using GitLab's automated rebasing when merging a merge request created
against a revision of master that's no longer the most recent revision).
--
Joseph S. Myers
joseph@codesourcery.com