GSoC Immutable Strings proposal proposal

[Jonathan Leto]

Howdy,

I think working in an svn branch in the main repo would be fine, or in
a pure git branch of of the Parrot github mirror (which I will fix
soon). I actually recommend against git-svn, since it adds unnecessary
complication.

I think whatever Nat wants to learn more about (svn or git) is what he
should use.

Duke

On Sun, Apr 4, 2010 at 4:51 AM, Andrew Whitworth <wknight8111 at gmail.com> wrote:
> That sounds a little bit unnecessary. I don't see any reason why he
> couldn't use a subversion branch in the main Parrot repo. I'm not
> taking a stand in the "git vs svn" debate, nor am I suggesting that
> one would be any easier than the other for the work. However, being in
> the main svn repo would have some proximity benefits, methinks.
>
> --Andrew Whitworth
>
>
>
> On Sun, Apr 4, 2010 at 2:42 AM, Nat Tuck <nat at ferrus.net> wrote:
>> Duke -
>>
>> I've updated my draft based on your suggestions.
>>
>>> Are you familiar with version control?  I think the deliverables
>>> section should describe that you will have a separate code repo that
>>> will then get merged. The best way to go about this is probably a git
>>> branch of the parrot git mirror (which i need to get running again,
>>> long story...), but you could also use a Subversion branch.
>>
>> I've been using subversion on projects for a while, but not to the point of
>> properly taking advantage of branching and merging. Doing a git branch
>> sounds reasonable. If the git mirror still isn't up, I there's supposedly
>> something called git-svn.
>>
>> -- Nat
>>
>> _______________________________________________
>> http://lists.parrot.org/mailman/listinfo/parrot-dev
>>
>>
>



-- 
Jonathan "Duke" Leto
jonathan at leto.net
http://leto.net