From: Felipe Contreras <email@example.com> To: Jonathan Nieder <firstname.lastname@example.org>, email@example.com Cc: Raxel Gutierrez <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Junio C Hamano <email@example.com>, Taylor Blau <firstname.lastname@example.org>, Emily Shaffer <email@example.com> Subject: RE: Pain points in Git's patch flow Date: Fri, 30 Apr 2021 16:09:53 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YHaIBvl6Mf7ztJB3@google.com> Jonathan Nieder wrote: > He'll be working on a bit of an experimental project: we want to take > Patchwork, which in principle can be a helpful addition to a > mailing list centric workflow, and improve it to be something that > people in the Git open source project get day-to-day benefit from. > Raxel's previous successes in making changes to tools to support a > better user experience make me excited for the potential for this > work. Raxel, I would consider looking at nmbug. It is a tool developed by the notmuch team in order to deal with patches both in command line and web interfaces. As you can see from the discussion that ensured from the original mail, the git community does care about the command line interface a great deal. > Those four are important in my everyday life. Questions: > > 1. What pain points in the patch flow for git.git are important to > you? My only real pain point is that sometimes a patch series is sent as a subthread of another patch series, which makes it difficult for me to mentally separate the two. > 2. What tricks do you use to get by with those existing pain points? There is nothing I can do. This is a culture thing that hopefully will change. > 3. Do you think patchwork goes in a direction that is likely to help > with these? No. > 4. What other tools would you like to see that could help? nmbug, but again, it depends on how it's actually used. Cheers.  https://notmuchmail.org/nmbug/ -- Felipe Contreras
prev parent reply other threads:[~2021-04-30 21:10 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-14 6:13 Jonathan Nieder 2021-04-14 7:22 ` Bagas Sanjaya 2021-04-14 8:02 ` Junio C Hamano 2021-04-14 21:42 ` Junio C Hamano 2021-04-15 8:49 ` Denton Liu 2021-04-15 6:06 ` Junio C Hamano 2021-04-15 15:45 ` Son Luong Ngoc 2021-04-19 2:57 ` Eric Wong 2021-04-19 13:35 ` Theodore Ts'o 2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:21 ` Eric Wong 2021-04-28 7:05 ` Eric Wong 2021-04-15 18:25 ` Atharva Raykar 2021-04-16 19:50 ` Junio C Hamano 2021-04-16 20:25 ` Junio C Hamano 2021-05-02 5:35 ` ZheNing Hu 2021-04-18 8:29 ` Sebastian Schuberth 2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason 2021-04-19 2:58 ` Eric Wong 2021-04-19 5:54 ` Sebastian Schuberth 2021-04-19 6:04 ` Sebastian Schuberth 2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:23 ` Sebastian Schuberth 2021-04-19 22:34 ` Theodore Ts'o 2021-04-20 6:30 ` Sebastian Schuberth 2021-04-20 16:37 ` Theodore Ts'o 2021-04-30 20:45 ` Felipe Contreras 2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:36 ` Eric Wong 2021-04-19 19:49 ` Sebastian Schuberth 2021-04-19 22:00 ` Konstantin Ryabitsev 2021-05-08 2:10 ` dwh 2021-04-19 21:49 ` Konstantin Ryabitsev 2021-04-19 23:03 ` Stephen Smith 2021-05-08 2:08 ` dwh 2021-05-08 4:41 ` Bagas Sanjaya 2021-04-30 20:58 ` Felipe Contreras 2021-04-21 4:46 ` Daniel Axtens 2021-04-26 2:04 ` brian m. carlson 2021-04-26 14:24 ` Theodore Ts'o 2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:59 ` Eric Wong 2021-04-28 22:44 ` brian m. carlson 2021-04-30 20:16 ` Felipe Contreras 2021-04-30 20:35 ` Felipe Contreras 2021-04-30 21:09 ` Felipe Contreras [this message]
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: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='RE: Pain points in Git'\''s patch flow' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).