All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How can I submit patch for bug #42944 ?
Date: Sat, 11 Oct 2014 10:47:44 +0200	[thread overview]
Message-ID: <5438EEB0.70308@gmail.com> (raw)
In-Reply-To: <CAN9vWDJoZZmz-Wq_zD178rb4P4n9FWaGyTBGOsfGLWhZXOPPYA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

On 11.10.2014 09:41, Michael Zimmermann wrote:
> @Colin I dunno if it's worth it for GRUB but did u ever think about a
> gerrit instance?
> It simplifies review a lot.
> 
It doesn't. It only simplifies approval. I'd be opposed to gerrit unless
there is a way to forbid non-admins to edit other people patches.
> On Fri, Oct 10, 2014 at 11:23 PM, Colin Watson <cjwatson@ubuntu.com
> <mailto:cjwatson@ubuntu.com>> wrote:
> 
>     On Fri, Oct 10, 2014 at 04:44:39PM +0000, Rigoberto Corujo wrote:
>     > I attached a patch to bug #42944 and would like to know how I would go about getting it committed to the source tree?
>     > https://savannah.gnu.org/bugs/?42944
> 
>     I'd suggest attaching the patch to a mail here (not encased in a zip
>     file).  It's usually easier to get public review that way.
> 
>     --
>     Colin Watson                                     
>      [cjwatson@ubuntu.com <mailto:cjwatson@ubuntu.com>]
> 
>     _______________________________________________
>     Grub-devel mailing list
>     Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     https://lists.gnu.org/mailman/listinfo/grub-devel
> 
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2014-10-11  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 16:44 How can I submit patch for bug #42944 ? Rigoberto Corujo
2014-10-10 21:23 ` Colin Watson
2014-10-11  7:41   ` Michael Zimmermann
2014-10-11  8:47     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-10-11  8:44   ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-10-11  8:58     ` Andrei Borzenkov
2014-10-12 16:24       ` Andrei Borzenkov
2014-10-13 16:35         ` Rigoberto Corujo
2014-10-14  0:06           ` Rigoberto Corujo
2014-10-17 14:29             ` Rigoberto Corujo
2014-10-21 19:41               ` Rigoberto Corujo

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=5438EEB0.70308@gmail.com \
    --to=phcoder@gmail.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.