bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57467: [EXT] Re: bug#57467: [EXT] Re: [EXT] Re: bug#57467: 'guix she


From: Thompson, David
Subject: bug#57467: [EXT] Re: bug#57467: [EXT] Re: [EXT] Re: bug#57467: 'guix shell' does not honor default behavior when given a specific command to run
Date: Tue, 30 Aug 2022 12:22:05 -0400

Hi Tobias,

On Tue, Aug 30, 2022 at 11:01 AM Tobias Geerinckx-Rice <me@tobias.gr> wrote:
Hi David,

Thompson, David 写道:
> The hostility here and in the other issue where you are applying
> stop energy to my work is less than appreciated.

Some healthy ‘stop energy’ was needed here, and in bug #56444.

It made me feel like my effort was not appreciated or wanted, so I don't think it was healthy.

In this case I made a mistake and I'm sorry.  I thought Maxime hadn't provided any context for saying something was a feature and not a bug, which is why I asked for clarification and direction so I wasn't at a dead end. I thought I was being dismissed. I tried to find a justification in the source code and couldn't find it, so I thought it couldn't hurt to just submit a patch and figure out what the issues might be.  It was a misunderstanding and I'd like to reset and return to talking through the technical issues of this bug report.
 
Please spend that energy on fleshing out requirements and
improving the patches if needed.  Maxime's review is a good start.

Yes, I agree now that I have the context that I missed the first time.
 
Shopping around for a ‘core dev’ to fast-track these patches
disrespects the work Maxime has already put in, and is not how
things are done.  It won't happen.

 I am not trying to fast track anything, and certainly not the patch here.  I am going to write a separate message to go over the competing desires for 'guix shell' that make my proposed behavior change potentially controversial.

Thanks,

- Dave

reply via email to

[Prev in Thread] Current Thread [Next in Thread]