From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-pe2elf
Date: Mon, 03 Aug 2009 16:29:18 -0400 [thread overview]
Message-ID: <1249331358.7265.6.camel@mj> (raw)
In-Reply-To: <d7ead6de0908030253o60e752f5r63be4966a1905904@mail.gmail.com>
On Mon, 2009-08-03 at 11:53 +0200, Vladimir 'phcoder' Serbinenko wrote:
> I personally think this is a hassle for nothing: we already have a
> working cygwin toolchain. While I acknowledge it's not perfect it
> works. And I propose not to touch it until it gives any maintainance
> or technical problem. When it does then we may consider dropping or
> limiting cygwin support. Until then this discussion is a waste of time
> (IMO)
I agree that there is no urgent need to remove grub-pe2elf (although the
issue might come up essentially). However, it's not so much a technical
problem as an issue of trust.
Committing code against the wish of maintainers should not be permitted.
Those who do it should lose commit access. They are welcome to
contribute, but their patches will need to be committed by others.
I haven't seen any apology or explanation in this thread.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-08-03 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 14:46 grub-pe2elf Robert Millan
2009-07-31 18:27 ` grub-pe2elf Christian Franke
2009-08-01 14:25 ` grub-pe2elf Robert Millan
2009-08-01 15:06 ` grub-pe2elf Christian Franke
2009-08-02 21:31 ` grub-pe2elf Robert Millan
2009-08-03 9:33 ` grub-pe2elf Christian Franke
2009-08-03 9:53 ` grub-pe2elf Vladimir 'phcoder' Serbinenko
2009-08-03 20:29 ` Pavel Roskin [this message]
2009-08-04 20:30 ` grub-pe2elf Robert Millan
2009-08-04 21:45 ` grub-pe2elf Christian Franke
2009-08-04 22:39 ` grub-pe2elf Robert Millan
2009-08-04 20:22 ` grub-pe2elf Robert Millan
2009-08-04 21:04 ` grub-pe2elf Christian Franke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249331358.7265.6.camel@mj \
--to=proski@gnu.org \
--cc=grub-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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.