From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Support for reading LVM volumes
Date: Tue, 15 Aug 2006 14:24:06 +0200 [thread overview]
Message-ID: <200608151424.07030.okuji@enbug.org> (raw)
In-Reply-To: <1155498700.18244.12.camel@diesel>
On Sunday 13 August 2006 21:51, Hollis Blanchard wrote:
> On Sun, 2006-08-13 at 20:23 +0200, Jeroen Dekkers wrote:
> > At Sun, 13 Aug 2006 11:49:06 -0500,
> >
> > Hollis Blanchard wrote:
> > > What will happen to the google-soc2006 CVS branch when you're done?
> >
> > It should be merged into the mainline.
>
> Well, of course. :) My question wasn't "what _should_ happen?" but
> rather "what _will_ happen?".
>
> Who is going to do this? Does this fall outside the scope of your SoC
> project? I understand that branches in CVS are extremely cumbersome, so
> will this be a difficult process?
Anybody can do this. If nobody else wants to do, I will do it...
BTW, it is not difficult to merge branches in CVS, if it is done only once.
What's difficult in CVS is to track what are merged and what are not merged.
In this case, the disadvantage does not matter.
Okuji
next prev parent reply other threads:[~2006-08-15 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 15:13 Support for reading LVM volumes Jeroen Dekkers
2006-08-13 16:49 ` Hollis Blanchard
2006-08-13 18:23 ` Jeroen Dekkers
2006-08-13 19:51 ` Hollis Blanchard
2006-08-13 20:08 ` Jeroen Dekkers
2006-08-13 23:06 ` moving away from CVS Hollis Blanchard
2006-08-14 5:38 ` Marco Gerards
2006-08-14 10:09 ` Johan Rydberg
2006-08-14 13:28 ` Marco Gerards
2006-08-15 12:24 ` Yoshinori K. Okuji [this message]
2006-08-15 11:30 ` Support for reading LVM volumes Jeroen Dekkers
2006-08-15 12:06 ` Marco Gerards
2006-08-15 12:48 ` Yoshinori K. Okuji
2006-08-15 21:16 ` Jeroen Dekkers
2006-09-03 13:16 ` Thomas Schwinge
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=200608151424.07030.okuji@enbug.org \
--to=okuji@enbug.org \
--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.