All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: please stop this
Date: Thu, 16 Jul 2009 17:23:13 +0200	[thread overview]
Message-ID: <20090716152313.GA6771@thorin> (raw)
In-Reply-To: <ca0f59980907141117s55a4ba09v1776f34163387e4d@mail.gmail.com>

On Wed, Jul 15, 2009 at 02:17:39AM +0800, Bean wrote:
> On Wed, Jul 15, 2009 at 2:09 AM, Pavel Roskin<proski@gnu.org> wrote:
> > On Tue, 2009-07-14 at 19:57 +0200, Robert Millan wrote:
> >
> >> I agree that we have a problem due to lack of leadership, but this is not
> >> acceptable.  Marco is busy right now (traveling), so please put this on hold
> >> untill he's back, then we can discuss it.
> >
> > I agree that we should not rush with such changes.  However, publishing
> > patches for discussion and testing is a good thing and should not be
> > discouraged.
> 
> Hi,
> 
> Yeah, I don't mean to push it. In fact, I've created a git repository
> for my temporary work
> 
> http://repo.or.cz/w/grub2/bean.git

Hi,

Usually, I only go through the trouble of implementing things when it's
clear they will be merged in some form.  But I understand it's not
the same for everyone.  So if I missunderstood, please accept my apology.

In any case, this kind of changes need wider consensus, and including the
maintainers in it.  And in general, I think we should hold off from big
restructuring at this time.  Using branches is a good idea IMHO (be it
"someone's branch" or "pupa2" or whatever).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-07-16 15:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 15:49 [PATCH] New object format Bean
2009-07-14 17:57 ` please stop this Robert Millan
2009-07-14 18:09   ` Pavel Roskin
2009-07-14 18:17     ` Bean
2009-07-16 15:23       ` Robert Millan [this message]
2009-07-16 16:10         ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:15           ` Robert Millan
2009-07-18 18:53             ` Vladimir 'phcoder' Serbinenko
2009-07-14 21:02 ` [PATCH] New object format Bean
2009-07-19  1:52 ` Isaac Dupree
2009-07-19 10:03   ` Bean
2009-07-21 20:55     ` Bean
2009-07-22 11:12       ` Bean
2009-07-22 11:47         ` Javier Martín
2009-07-22 13:34           ` Bean
2009-07-22 13:42             ` Javier Martín
2009-07-22 14:52               ` Bean
2009-07-25 19:33                 ` Bean
2009-07-27 18:41                   ` Bean
2009-07-28 11:00                     ` Bean
2009-07-30 14:51                       ` Bean
2009-07-31 18:10                         ` Bean
2009-08-05 17:59                           ` Bean
2009-08-07 17:18                             ` Bean
2009-08-09 19:10                               ` Bean

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=20090716152313.GA6771@thorin \
    --to=rmh@aybabtu.com \
    --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.