All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-pe2elf
Date: Tue, 04 Aug 2009 23:45:45 +0200	[thread overview]
Message-ID: <4A78AC09.2000705@t-online.de> (raw)
In-Reply-To: <20090804203022.GC15811@thorin>

Robert Millan wrote:
> On Mon, Aug 03, 2009 at 04:29:18PM -0400, Pavel Roskin wrote:
>   
>> 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 agree...


>> I haven't seen any apology or explanation in this thread.
>>     
>
>   

... but I will not apologize simply because I did not commit the 
grub-pe2elf patch.


> Yes, this is what worries me the most.
>
>   

I'm somewhat worried that these complaints are delayed by more than a year
Commit 1726 is from 2008-07-24, start was here:
http://lists.gnu.org/archive/html/grub-devel/2008-07/msg00452.html


-- 
Regards,
Christian Franke




  reply	other threads:[~2009-08-04 21:45 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             ` grub-pe2elf Pavel Roskin
2009-08-04 20:30               ` grub-pe2elf Robert Millan
2009-08-04 21:45                 ` Christian Franke [this message]
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=4A78AC09.2000705@t-online.de \
    --to=christian.franke@t-online.de \
    --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.