You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by David Lutterkort <lu...@redhat.com> on 2011/01/04 00:25:09 UTC
Re: patch for gogrid driver
On Fri, 2010-12-31 at 15:13 +0100, Adrian Cole wrote:
> I'm unsure of the status of issues, and such. There's a small bug in
> the gogrid driver, I've attached a patch for. Basically, the
> description of an image can be null, and currently breaks parsing of
> the architecture field.
>
> Please let me know the best process for submitting patches.
The preferred way to submit patches is by sending them to the mailing
list, ideally using 'git send-email', but for simple patches, just a
unified diff attached to an email is fine, too.
David
Re: patch for gogrid driver
Posted by Adrian Cole <fe...@gmail.com>.
Hi, guys.
Thanks for answering. The way I handle patches to Whirr, for example,
is the means Craig mentioned: unified diff off svn, and attach to a
Jira. I'm fine with this, if someone confirms this is how Delta wants
to work :)
-A
On Tue, Jan 4, 2011 at 2:37 AM, Stephen Gordon <sg...@redhat.com> wrote:
> On 01/04/2011 11:22 AM, Craig L Russell wrote:
>>
>> Generally, the best way to submit patches for projects at Apache is to
>> open a JIRA bug report and attach the patch to the report. This makes it
>> easy to establish that the patch is intended as a contribution (there's
>> a tick box that explicitly identifies the patch as intended by the
>> submitter as a contribution).
>>
>> The JIRA creation and update will be sent to the dev list so there's no
>> need to send it to the dev list as well...
>
> Perhaps if this is indeed the preferred procedure it should be mentioned on
> the relevant section of the website?:
>
> http://incubator.apache.org/deltacloud/contribute.html
>
>>
>> Craig
>>
>> On Jan 3, 2011, at 3:25 PM, David Lutterkort wrote:
>>
>>> On Fri, 2010-12-31 at 15:13 +0100, Adrian Cole wrote:
>>>>
>>>> I'm unsure of the status of issues, and such. There's a small bug in
>>>> the gogrid driver, I've attached a patch for. Basically, the
>>>> description of an image can be null, and currently breaks parsing of
>>>> the architecture field.
>>>>
>>>> Please let me know the best process for submitting patches.
>>>
>>> The preferred way to submit patches is by sending them to the mailing
>>> list, ideally using 'git send-email', but for simple patches, just a
>>> unified diff attached to an email is fine, too.
>>>
>>> David
>>>
>>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> Chair, OpenJPA PMC
>> clr@apache.org http://db.apache.org/jdo
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: patch for gogrid driver
Posted by Stephen Gordon <sg...@redhat.com>.
On 01/04/2011 11:22 AM, Craig L Russell wrote:
> Generally, the best way to submit patches for projects at Apache is to
> open a JIRA bug report and attach the patch to the report. This makes it
> easy to establish that the patch is intended as a contribution (there's
> a tick box that explicitly identifies the patch as intended by the
> submitter as a contribution).
>
> The JIRA creation and update will be sent to the dev list so there's no
> need to send it to the dev list as well...
Perhaps if this is indeed the preferred procedure it should be mentioned
on the relevant section of the website?:
http://incubator.apache.org/deltacloud/contribute.html
>
> Craig
>
> On Jan 3, 2011, at 3:25 PM, David Lutterkort wrote:
>
>> On Fri, 2010-12-31 at 15:13 +0100, Adrian Cole wrote:
>>> I'm unsure of the status of issues, and such. There's a small bug in
>>> the gogrid driver, I've attached a patch for. Basically, the
>>> description of an image can be null, and currently breaks parsing of
>>> the architecture field.
>>>
>>> Please let me know the best process for submitting patches.
>>
>> The preferred way to submit patches is by sending them to the mailing
>> list, ideally using 'git send-email', but for simple patches, just a
>> unified diff attached to an email is fine, too.
>>
>> David
>>
>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> Chair, OpenJPA PMC
> clr@apache.org http://db.apache.org/jdo
>
>
>
>
>
>
>
>
>
Re: patch for gogrid driver
Posted by Craig L Russell <cr...@oracle.com>.
Generally, the best way to submit patches for projects at Apache is to
open a JIRA bug report and attach the patch to the report. This makes
it easy to establish that the patch is intended as a contribution
(there's a tick box that explicitly identifies the patch as intended
by the submitter as a contribution).
The JIRA creation and update will be sent to the dev list so there's
no need to send it to the dev list as well...
Craig
On Jan 3, 2011, at 3:25 PM, David Lutterkort wrote:
> On Fri, 2010-12-31 at 15:13 +0100, Adrian Cole wrote:
>> I'm unsure of the status of issues, and such. There's a small bug in
>> the gogrid driver, I've attached a patch for. Basically, the
>> description of an image can be null, and currently breaks parsing of
>> the architecture field.
>>
>> Please let me know the best process for submitting patches.
>
> The preferred way to submit patches is by sending them to the mailing
> list, ideally using 'git send-email', but for simple patches, just a
> unified diff attached to an email is fine, too.
>
> David
>
>
Craig L Russell
Secretary, Apache Software Foundation
Chair, OpenJPA PMC
clr@apache.org http://db.apache.org/jdo