Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Experimental branch of GRUB
Date: Sat, 31 Oct 2009 19:45:10 +0100	[thread overview]
Message-ID: <1257014710.3186.35.camel@fz.local> (raw)
In-Reply-To: <4AEC82E0.3010107@gmail.com>

Am Samstag, den 31.10.2009, 19:33 +0100 schrieb Vladimir 'phcoder'
Serbinenko:
> Felix Zielcke wrote:
> > Am Samstag, den 24.10.2009, 15:06 +0200 schrieb Robert Millan:
> >   
> >> An experimental branch of GNU GRUB is now available:
> >>
> >>     
> > [...]
> >   
> >> I'm appointing Vladimir Serbinenko as the developer in charge of this branch.
> >> Patches may be merged in it at his discretion. 
> >>     
> >
> > Vladimir whats your policy for merging trunk into experimental?
> > Do you want to track it on your own to keep them in sync?
> >
> >
> >   
> As nyu said everything which is ok for mainline is ok for experimental
> and so the only issue are conflicts but in practice any sane way to
> resolve them is ok. So I feel like no discussion should be necessary
> about this
> 

Well my question was mainly `Do you want to merge trunk into it or can
anyone of us do it?'
But seems like so :)


-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer




  reply	other threads:[~2009-10-31 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24 13:06 Experimental branch of GRUB Robert Millan
2009-10-31 14:49 ` Felix Zielcke
2009-10-31 15:33   ` Robert Millan
2009-10-31 18:33   ` Vladimir 'phcoder' Serbinenko
2009-10-31 18:45     ` Felix Zielcke [this message]
2009-10-31 19:16       ` Vladimir 'phcoder' Serbinenko
2009-10-31 18:37 ` Vladimir 'phcoder' Serbinenko
2009-10-31 19:07   ` Robert Millan

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=1257014710.3186.35.camel@fz.local \
    --to=fzielcke@z-51.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox