All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split of the normal mode
Date: Sun, 29 Mar 2009 13:53:12 +0300	[thread overview]
Message-ID: <49CF5318.2070607@nic.fi> (raw)
In-Reply-To: <49CF50D5.4060308@gmail.com>

Here I must comment that in some cases it is favorable to do it this
way. I personally will only commit changes that I am happy to live with.
Even if you are developer with SVN commit rights it is in some cases
good idea to have general review of the patch... but there has been some
lack of the time from people to review them (and it does not cross
everyones interest zones, thus get attention to the patch).

phcoder wrote:
> I'm actually quite unhappy with the grub's authority in general. Some
> people can commit their patches after a week of no replies while others
> like me have to wait that someone has time to review their patches in
> depth. I already have a collection of patches that are not commited, not
> because someone objects against them but just because nobody qualified
> enough has time to review and commit it. All this despite having already
> signed copyright assignment which because of slowness of FSF took more
> time than it should. From developer viewpoint it's very frustrating
> experience. If I wasn't so motivated as I am I would have already given
> up. IMO opinion if we want people coding for grub2 this has to be
> changed. But now you come and say you want to revert some patches just
> because they seem useless to you or rewrite some code just because you
> find it ugly or because it has a minor bug which could be easily fixed
> without rewriting. IMO this can easily drive developers to fork or leave
> project altogether. And additionally your energy would be much better
> spent in writing new stuff and making/reviewing design propositions than
> rewriting chunks of already working code.
> Sorry for being somewhat rude but I really find it frustrating this
> coder-unfriendliness
>> In brief, I take back the leadership of this project for general
>> directions. For some subsystems (e.g. the coreboot support), I
>> continue leaving the responsibility to those who know better or are
>> more active. Once the current code is reviewed and fixed (at some
>> degree), I will make a new release.
>>
>> Any objection?
>>
>> Regards,
>> Okuji
> 
> 




  reply	other threads:[~2009-03-29 10:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29  9:25 [PATCH] Split of the normal mode Bean
2009-03-29  9:40 ` Vesa Jääskeläinen
2009-03-29 10:09   ` Yoshinori K. Okuji
2009-03-29 10:43     ` phcoder
2009-03-29 10:53       ` Vesa Jääskeläinen [this message]
2009-03-29 11:33         ` phcoder
2009-03-29 11:51           ` Yoshinori K. Okuji
2009-03-29 12:09             ` Bean
2009-03-29 13:10               ` Yoshinori K. Okuji
2009-03-29 13:59                 ` Bean
2009-03-29 14:20                   ` Yoshinori K. Okuji
2009-03-29 14:30                     ` Bean
2009-03-29 14:54                       ` Yoshinori K. Okuji
2009-03-29 15:17                         ` Bean
2009-03-30 15:42                           ` Yoshinori K. Okuji
2009-03-30 20:04                 ` Colin D Bennett
2009-03-31  6:11                   ` Bean
2009-03-31 15:02                     ` Colin D Bennett
2009-03-29 13:00             ` phcoder
2009-03-29 14:51               ` Yoshinori K. Okuji
2009-03-29 17:07                 ` phcoder
2009-03-29 20:35                   ` phcoder
2009-03-30 15:49                     ` Yoshinori K. Okuji
2009-03-30 15:59                       ` phcoder
2009-04-01  7:43                         ` phcoder
2009-04-01  8:07                           ` David Miller
2009-04-01  9:22                             ` phcoder
2009-04-01 14:10                               ` Yoshinori K. Okuji
2009-04-01 16:14                                 ` phcoder
2009-03-29 11:29       ` Yoshinori K. Okuji
2009-03-29 11:40         ` David Miller
2009-03-29 12:55           ` Yoshinori K. Okuji
2009-03-29 13:23             ` Vesa Jääskeläinen
2009-03-29 14:49               ` Yoshinori K. Okuji
2009-03-29 15:43                 ` Vesa Jääskeläinen
2009-03-29 20:26               ` David Miller
2009-03-29 20:24             ` David Miller
2009-03-29 20:38               ` phcoder
2009-03-30 15:43                 ` Bean
2009-03-30 16:22                   ` Yoshinori K. Okuji
2009-03-30 16:38                     ` Bean
2009-03-30 16:35                   ` Vesa Jääskeläinen
2009-03-29 11:59         ` General design (was Re: [PATCH] Split of the normal mode) phcoder
2009-03-29 10:48     ` [PATCH] Split of the normal mode Vesa Jääskeläinen
2009-03-29 11:39       ` Yoshinori K. Okuji
2009-03-29 12:17       ` Vesa Jääskeläinen
2009-04-01 13:19     ` Robert Millan
2009-04-01 14:15       ` Yoshinori K. Okuji

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=49CF5318.2070607@nic.fi \
    --to=chaac@nic.fi \
    --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.