Josh,

On 6/7/06, Joshua Uziel <joshua.uziel at sun.com> wrote:
> So, it's time to think about sending you guys the code.  Right now,
> we're going through and cleaning things up a little, doing the legal
> process and whatnot, but what we've got should be in your hands in the
> near future.  What I want to talk about is what form you guys want it in.
>

First of all that is great - frankly speaking I started to fear we'll never
see the actual source ;-)

As for the form of the code - why don't you just create your own branch
in svn and work out of it ? That way it will be easier for everyone,
yourself included. It allows you to move at your own pace and
merge when you ready and feel comfortable.

Speaking more generally - Polaris source base would most probably
move to mercurial together with the ON consolidation. So depending
on what time frame you are targeting for source contribution you
may or may not want to invest into Subversion.

Failing all these - the option no. 1 from your list appears sane at most
to me.

[more below]

> We originally started working off of Cyril's tree at
>
>    http://svn.genunix.org/repos/polaris/branches/boot
>
> as checked out on March 10th.  From there, we have changes that amount
> to a 40,000 line patch that is 1MB in size.  What my question is, when
> the time comes, how would you like it?  The three best options:
>
> 1) A patch against that same tree.  This is quick and trivial to do and
> will take pretty much no effort.  From there, it's just a matter of
> merging it in and syncing it back into the trunk.  It's not against the
> latest OpenSolaris bits, but merging them together shouldn't be too
> bad... and that's something the Polaris project should have someone
> responsible for going forward.  This at least has the advantage that we
> have it in subversion from the get go.
>
> 2) A tarball of our whole tree as we have it right now.  That also isn't
> against the latest OpenSolaris builds, and someone will have to do the
> merging work.
>
> 3) A patch against a more recent OpenSolaris tarball.  This would be a
> good starting point for a fresh tree, but you'll all have to wait a bit
> longer while I do the merge.  Did I mention I like options 1 and 2
> better? :)
>
> But yeah, bringing back my point in option 1 is that someone should keep
> the working Polaris tree up to date with the latest OpenSolaris builds
> as they become available.  There's also the question of if there's

Right, I used to do it, but was quite too busy during last couple of months :(

> somewhere you guys would prefer to host it other than
> http://svn.genunix.org/ ...  we're flexible.

Why ? svn.genunix.org works fine and the only change I envision
is to migrate to Mercurial when the time comes.


-- 
Regards,
        Cyril

Reply via email to