From: "Ludovic Courtès" <ludo@gnu.org>
To: "Filip Łajszczak" <filip@lajszczak.dev>
Cc: guix-devel@gnu.org
Subject: Re: Formalizing teams
Date: Mon, 03 Jan 2022 16:09:38 +0100 [thread overview]
Message-ID: <87tuekj1ot.fsf@gnu.org> (raw)
In-Reply-To: <55797e3b-2032-4282-5a29-48748d8c1dbb@lajszczak.dev> ("Filip Łajszczak"'s message of "Wed, 22 Dec 2021 19:43:56 +0000")
Hello,
Filip Łajszczak <filip@lajszczak.dev> skribis:
> Great idea. As a newcomer who created his first patch in May
> https://issues.guix.gnu.org/issue/48289/ that got a review, was fixed
> and submitted again, and then disappeared into oblivion, I would be
> very happy to be able to ask some "Python packaging" team what is
> wrong with my patch. At the same time I'm grateful for everything that
> is being done all the time, so I'm not in a position to put any
> pressure on anyone. (BTW, I resubmitted it in the new style after The
> Big Change)
Oh, at least pinging people explicitly after some time has passed is
much welcome! Hopefully someone will actually take a look this time…
Ludo’.
next prev parent reply other threads:[~2022-01-03 15:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:46 Formalizing teams Ludovic Courtès
2021-12-22 16:04 ` Jack Hill
2021-12-22 16:22 ` indieterminacy
2021-12-22 19:43 ` Filip Łajszczak
2022-01-03 15:09 ` Ludovic Courtès [this message]
2021-12-27 5:17 ` Maxim Cournoyer
2021-12-28 10:52 ` Lars-Dominik Braun
2021-12-28 15:44 ` Kyle Meyer
2021-12-28 18:03 ` Ricardo Wurmus
2021-12-29 21:04 ` Lars-Dominik Braun
2021-12-28 14:44 ` Ricardo Wurmus
2021-12-29 9:05 ` Efraim Flashner
2022-01-03 15:22 ` Ludovic Courtès
2022-01-03 15:57 ` Ricardo Wurmus
2022-01-04 22:35 ` adriano
2022-03-31 21:15 ` david larsson
2022-04-01 9:14 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 15:13 Blake Shaw
2021-12-23 21:51 ` Jonathan McHugh
2021-12-24 12:23 ` Hartmut Goebel
2021-12-24 15:37 ` indieterminacy
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=87tuekj1ot.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=filip@lajszczak.dev \
--cc=guix-devel@gnu.org \
/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).