grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Support for reading LVM volumes


From: Jeroen Dekkers
Subject: Re: Support for reading LVM volumes
Date: Sun, 13 Aug 2006 22:08:20 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shij┼Ź) APEL/10.6 Emacs/22.0.50 (x86_64-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Sun, 13 Aug 2006 14:51:40 -0500,
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?

You don't have to really merge the branch in CVS. You can just call
diff on both branches and apply the patch on the mainline. Of course
this isn't the most beautiful way, but it works... 

I also think we should switch to a better VCS. I'm actually using bzr
myself. If anyone is interested, I've published my SoC branch and the
CVS on my homepage:
http://dekkers.cx/bzr/grub2
http://dekkers.cx/bzr/grub2-cvs

My preference is bzr, but almost everything is better than cvs. I
would happily use svn, mercurial or darcs for example.

Jeroen Dekkers




reply via email to

[Prev in Thread] Current Thread [Next in Thread]