From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Google's Summer of Code 2008 / GRUB 2
Date: Thu, 24 Apr 2008 20:13:25 +0300 [thread overview]
Message-ID: <4810BFB5.6020200@nic.fi> (raw)
In-Reply-To: <87ve277q8v.fsf@xs4all.nl>
Marco Gerards wrote:
> Vesa Jääskeläinen <chaac@nic.fi> writes:
>>> First of all, the code. I think it would be a good idea if I would
>>> send in patches for my code so it will be immediately integrated into
>>> GRUB 2. This would work as everyone will make sure that this code
>>> will not be touched by anyone and patches to this will be ignored.
>>> Otherwise I can work in a branch, my own bzr repository or whatever.
>>> I hope I will get feedback on this :-)
>> Please remember that after GSoC coding period is over you have to
>> upload your code to Google Code as per:
>>
>> 12. Student uploads completed code to a Google Code hosted project.
>>
>> http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_program_works
>
> Yes, I know. All I upload has to be my code. But working in CVS is
> not a problem, as long as nobody touches my code. Otherwise I have to
> keep it separate and merge at the end of the project. So I can post
> small pieces of code and merge often, or merge at once at the end.
> What is preferred?
Although we have people that would like to test out your code while in
development, lets keep it clean for every party what is yours and what
is not. So use git, bzr, or what ever tool and try to keep in sync with
HEAD. In meanwhile you can provide patches or tarballs of your build if
people want to test it out.
When GSoC is completed then we will merge your code. Anyway, I think it
will be quite isolated in yours case.
And also what Robert said about stability...
Thanks,
Vesa Jääskeläinen
next prev parent reply other threads:[~2008-04-24 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:00 Google's Summer of Code 2008 / GRUB 2 Vesa Jääskeläinen
2008-04-22 0:39 ` Colin D Bennett
2008-04-22 21:49 ` Pavel Roskin
2008-04-24 7:49 ` Robert Millan
2008-04-23 9:47 ` Marco Gerards
2008-04-23 13:53 ` Colin D Bennett
2008-04-23 21:37 ` Vesa Jääskeläinen
2008-04-24 5:53 ` Marco Gerards
2008-04-24 17:13 ` Vesa Jääskeläinen [this message]
2008-04-24 7:54 ` 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=4810BFB5.6020200@nic.fi \
--to=chaac@nic.fi \
--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.