From: Nils Landt <nils@landt.email>
To: jgart <jgart@dismail.de>, 71870@debbugs.gnu.org
Subject: bug#71870: Some broken Go packages (including Podman)
Date: Tue, 2 Jul 2024 08:20:42 +0200 (CEST) [thread overview]
Message-ID: <479449617.175721.1719901242517@office.mailbox.org> (raw)
In-Reply-To: <35d9a037be458b7f3e9b88ddbf9c7b877bfe9028@dismail.de>
> jgart <jgart@dismail.de> hat am 01.07.2024 19:04 CEST geschrieben:
>
>
> > No, the patch submission process is too annoying for me.
> >
>
> Hi Nils,
>
> Sorry to hear that. I can relate to that as I've also been annoyed by aspects of the process.
>
> Can you share some of the pain points that you've experienced with the patch submission process?
>
> This will help us potentially address that and open discussion around it.
>
> How do you think that the patch submission process can be improved?
Nothing that hasn't been talked about for years, really.
- Patch submission workflow without email
- Code review tool with threaded at-code conversations
- Code formatter that I can make work for vim (i.e. guix style for non-packages)
- Useful commit messages instead of GNU ChangeLog
My previous attempt at contribution (https://issues.guix.gnu.org/66557) was quite unpleasant.
I don't know how to phrase my critique of the reviewers in a constructive manner, given that I respect we're all human beings volunteering time for this hobby.
> I'm going to give a talk in August at the Guix London meetup on patch review, the mumi CLI tool, and my current personal workflow.
I will be watching the recording, but I don't see how it would address my wishlist :)
next prev parent reply other threads:[~2024-07-02 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 7:35 bug#71870: Some broken Go packages (including Podman) Nils Landt
2024-07-01 14:35 ` jgart via Bug reports for GNU Guix
2024-07-01 14:43 ` Nils Landt
2024-07-01 17:04 ` jgart via Bug reports for GNU Guix
2024-07-02 6:20 ` Nils Landt [this message]
2024-07-02 10:03 ` woshilapin
2024-07-02 15:16 ` jgart via Bug reports for GNU Guix
2024-07-03 16:40 ` Jean-Pierre De Jesus Diaz
2024-07-04 6:51 ` Nils Landt
2024-07-12 15:34 ` Sharlatan Hellseher
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=479449617.175721.1719901242517@office.mailbox.org \
--to=nils@landt.email \
--cc=71870@debbugs.gnu.org \
--cc=jgart@dismail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).