Mark,
Provided someone acts as the gatekeeper and patches don't disappear into
the bog of eternal stench, mailing 'em to the list works just fine for
me.
On Tue, 2008-11-25 at 12:38 +1100, Mark Goodwin wrote:
>
> Nathan Scott wrote:
> > On Tue, 2008-11-25 at 11:12 +1100, Ken McDonell wrote:
> >> On Tue, 2008-11-25 at 09:38 +1100, Nathan Scott wrote:
> >>> ...
> >> I have a patch to fix this (missing endian conversion from the year
> >> dot).
> >>
> >> Patch is attached, which raises the question of the "correct" protocol
> >> for bozos outside the sgi-aconex consortium to get pcp patches into the
> >> one true official tree ... guidance?
> >
> > 1. Clone yerself a git tree from git://oss.sgi.com/pcp/pcp.git
> > 2. Create a branch for development
> > 3. Code, test, commit patches locally
> > 4. Push changes out to a visible server
> > 5. Send mail to pcp@xxxxxxxxxxx with updates
> >
> > Probably best if you re-activate your account on oss.sgi.com,
> > unless you have a local server you can use for exporting your
> > git tree to the world?
>
> You can just post the patch to the list for review if you want, and
> if accepted, Jonathan will push it back out to the 'dev' branch at
> git://oss.sgi.com/pcp/pcp.git
>
> > Then, people (esp. Jonathan / myself) can pull in your changes
> > regularly and I'd expect 'em to appear in the next release.
>
> They'll appear in the next release (whenever that happens to be),
> but more expediently, in the dev branch as soon as Jonathan pushes
> back out to oss (which would be daily or on demand as needed).
>
> I can get oss accounts created if needed, but I'm wondering if
> we could maybe have a semi-open-access 'incoming' repository or
> something for those without a net visible server ..? Or will simply
> mailing patches to pcp@oss suffice?
>
> Cheers
> -- Mark
|