Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeffrey Walton via Gdb <gdb@sourceware.org>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: Joseph Myers <josmyers@redhat.com>,
	gcc@gcc.gnu.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gdb@sourceware.org,
	 "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: On pull request workflows for the GNU toolchain
Date: Mon, 23 Sep 2024 08:53:50 -0400	[thread overview]
Message-ID: <CAH8yC8=8kn+PpLLJox2tFq24gHMfpAk9x-GaLXofJje3WRN93A@mail.gmail.com> (raw)
In-Reply-To: <55715cf9-0f6c-4525-a310-7945db72dc21@netcologne.de>

On Mon, Sep 23, 2024 at 8:08 AM Thomas Koenig via Gdb
<gdb@sourceware.org> wrote:
>
> [For the fortran people: Discussion on gcc@]
>
> Just a general remark.
>
> There are people, such as myself, who regularly mess up
> their git repositories because they have no mental model
> of what git is doing (case in point: The Fortran unsigned
> branch, which I managed to put into an unrepairable state
> despite considerable help from people who tried to help me
> fix it). This is especially true of volunteer maintainers,
> who are still the mainstay of gfortran.

++.

Thousands of upvotes on Stack Overflow questions about simple Git
tasks indicate usability problems in Git, and not a great question on
social media. Confer, <https://meta.stackoverflow.com/q/351700>.

> Whatever you end up doing, consider such maintainers, and
> if they still can contribute or would simply give up.
> If what you end up doing is too complicated, it may end up
> severely impacting the gfortran project (and possibly others).

Jeff

  reply	other threads:[~2024-09-23 12:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 15:51 Joseph Myers via Gdb
2024-09-20 18:25 ` Carlos O'Donell via Gdb
2024-09-20 20:41   ` Joseph Myers via Gdb
2024-09-20 21:43   ` Sam James via Gdb
2024-09-20 19:58 ` Matt Rice via Gdb
2024-09-20 20:47   ` Joseph Myers via Gdb
2024-09-23 12:07 ` Thomas Koenig via Gdb
2024-09-23 12:53   ` Jeffrey Walton via Gdb [this message]
2024-09-23 13:23   ` Jonathan Wakely via Gdb
2024-09-23 13:36     ` enh via Gdb
2024-09-23 14:33       ` Jonathan Wakely via Gdb
2024-09-23 15:56         ` Iain Sandoe
2024-09-23 15:03       ` Joseph Myers via Gdb
2024-09-23 15:20     ` Florian Weimer via Gdb
2024-09-23 15:44       ` Jonathan Wakely via Gdb
2024-09-23 17:57   ` Eric Gallager via Gdb
2024-09-23 18:39     ` Jonathan Wakely via Gdb
2024-09-23 18:30   ` Arsen Arsenović via Gdb
2024-09-23 12:56 ` Richard Earnshaw (lists) via Gdb
2024-09-23 14:59   ` Joseph Myers via Gdb
2024-09-24  3:43 ` Jiang, Haochen via Gdb
2024-09-24 16:42   ` Joseph Myers via Gdb
2024-09-25  3:01     ` Jiang, Haochen via Gdb
2024-09-25 14:46       ` Joseph Myers via Gdb
2024-09-26  1:42         ` Jiang, Haochen via Gdb

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8yC8=8kn+PpLLJox2tFq24gHMfpAk9x-GaLXofJje3WRN93A@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=josmyers@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=noloader@gmail.com \
    --cc=tkoenig@netcologne.de \
    /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