From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Tobias Kortkamp <tobias.kortkamp@gmail.com>, guix-devel@gnu.org
Subject: Re: Dealing with upstream issues
Date: Tue, 28 Jun 2022 18:47:27 +0200 [thread overview]
Message-ID: <18a9e93532a2f59d4ad5d6eb5343fe59248103fc.camel@telenet.be> (raw)
In-Reply-To: <86letgep2i.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
zimoun schreef op di 28-06-2022 om 18:21 [+0200]:
> And… as I wrote [1]:
>
> I agree; we cannot fix the world. ;-) In the case of patch#55541, the
> issues of cross-compilation can be reported directly to upstream and
> another Debbugs number could be open.
>
> 1: <https://yhetil.org/guix/87wnd2w9mm.fsf@gmail.com>
>
>
> The bug is not ignored, to the contrary.
It is -- where's the bug report upstream or a fix?
> But it is not a blocker for patch inclusion and so patch#55541 can be closed.
It is a blocker -- as previousy mentioned, upstream doesn't even know
about the bug.
> You are free, as the reviewer, to open a report for Guix pointing the
> issue of cross-compilation of ’azpainter’;
As mentioned previously, that is not reviewing, and I don't have time
to fix the world. I have other things to do than only acting on guix-
patches@. Also, as mentioned previously, can't a reviewer do a partial
review? Why the insistence on the reviewer -- isn't making a proper
patch the submitter's job, not the reviewer's?
> Well, you and me spend more time in discussing that than in just
> reporting the issue. ;-)
Yes, but if I just give in and report the issue after other insist I do
it, then I create the expectation that I'll just do everything. I
refuse, I insist on being allowed to quit doing something and start
doing other things.
(So TBC, I won't be doing that.)
> Ultimately, nothing is perfect and people are doing their best with
> their resource at hand; at least, I do my best with the resource at
> my hands. I would be more than happy if more people would try to
> sort, classify or fix the old bugs. Maybe, you will join the effort
> ?
I would have more time for that if we refused patches with issues like
this one and did not insist on letting the reviewer do the submittter's
job.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-28 16:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d31ff958ec0c75cbba8324a275315d195a54902.1653045472.git.tobias.kortkamp@gmail.com>
[not found] ` <87sfntu6ft.fsf@gnu.org>
[not found] ` <b6d482002f7773e65e02dbbbf354e1c0178b823a.camel@telenet.be>
2022-06-27 10:10 ` Dealing with upstream issues Ludovic Courtès
2022-06-27 10:30 ` Maxime Devos
2022-06-27 10:37 ` Maxime Devos
2022-06-27 12:32 ` zimoun
2022-06-27 14:20 ` Maxime Devos
2022-06-27 15:06 ` zimoun
2022-06-27 15:41 ` Maxime Devos
2022-06-28 11:01 ` zimoun
2022-06-28 12:21 ` Maxime Devos
2022-06-28 16:21 ` zimoun
2022-06-28 16:47 ` Maxime Devos [this message]
2022-06-28 17:36 ` zimoun
2022-06-28 20:03 ` Maxime Devos
2022-06-28 12:22 ` Maxime Devos
2022-06-28 12:31 ` Maxime Devos
2022-06-28 16:25 ` zimoun
2022-06-28 16:47 ` Maxime Devos
2022-06-29 6:07 ` bokr
2022-06-29 7:29 ` Missing tags in Debbugs? zimoun
2022-06-29 13:45 ` Bengt Richter
2022-06-30 11:53 ` Dealing with upstream issues Ludovic Courtès
2022-06-27 12:53 ` zimoun
2022-06-27 14:32 ` Maxime Devos
2022-06-27 15:23 ` zimoun
2022-06-27 15:47 ` Maxime Devos
2022-06-27 16:03 ` Maxime Devos
2022-06-27 16:14 ` Maxime Devos
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=18a9e93532a2f59d4ad5d6eb5343fe59248103fc.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=tobias.kortkamp@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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).