From: Elena Zannoni <elena.zannoni@oracle.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, Frysk List <frysk@sourceware.org>
Subject: Re: meeting
Date: Fri, 25 Jul 2008 13:11:00 -0000 [thread overview]
Message-ID: <4889CF65.1090307@oracle.com> (raw)
In-Reply-To: <48879E2E.5040200@redhat.com>
Questions/comments:
1. how come not just a simple branch of gdb? It would seem the simplest
alternative for doing merges?
2. I think a wise idea would be to settle on a set of host/targets
combinations that should always work on
archer. Ie those should be tested before doing a check in.
elena
Phil Muldoon wrote:
>
>> * Where to host? Lots of hosting choices out there, but sourceware
>> seems like the default. We all have accounts, we have access, etc.
>> I'd like to get things set up ASAP, say today.
>>
>>
> As neutral a place as possible, without any distro or company related
> connotations if possible . We have folks that can admin sourceware.org
> and it has proven highly successful as a place to host, develop and
> promote open source software. That is my vote.
>
>> - All patches must be reviewed by someone other than the author.
>> - I forgot to mention this, but Apache-like, a strong objection
>> should stall a patch until a rough consensus is reached.
>>
>
> Is the +1, -1 or (abstain) system?
>
>> - Proposed patch review guidelines:
>> * Does it have internal documentation (comments)?
>> * Does it follow upstream coding style?
>> * Does it have external documentation, if needed?
>> * Does it have a test case, if needed?
>> * Is it clear/complete/etc?
>>
>>
>
> Does it cause regressions to the existing test suite? Though this
> should be formed as a promise from the user that testing has occurred,
> re meeting.
>
> Regards
>
> Phil
>
--
Elena Zannoni, Oracle
Senior Engineering Manager, Tools/Languages - Linux Engineering
Blog: http://blogs.oracle.com/ezannoni
Email: elena.zannoni@oracle.com
next prev parent reply other threads:[~2008-07-25 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 21:21 meeting Tom Tromey
2008-07-23 20:04 ` meeting Tom Tromey
2008-07-23 20:39 ` meeting Tom Tromey
2008-07-23 21:10 ` meeting Phil Muldoon
2008-07-25 13:11 ` Elena Zannoni [this message]
2008-07-25 16:32 ` meeting Tom Tromey
2008-07-23 22:12 ` meeting Tom Tromey
2008-07-24 18:45 ` meeting Tom Tromey
2008-07-25 13:06 ` meeting Elena Zannoni
2008-07-25 16:33 ` meeting Tom Tromey
2008-07-27 14:49 ` meeting Eric Bachalo
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=4889CF65.1090307@oracle.com \
--to=elena.zannoni@oracle.com \
--cc=frysk@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).