From: Ralf Baechle <ralf@oss.sgi.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Adding code to the tree...
Date: Thu, 21 Feb 2002 02:51:21 +0100 [thread overview]
Message-ID: <20020221025121.A29466@dea.linux-mips.net> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAICEKCCFAA.mdharm@momenco.com>; from mdharm@momenco.com on Wed, Feb 20, 2002 at 05:38:59PM -0800
On Wed, Feb 20, 2002 at 05:38:59PM -0800, Matthew Dharm wrote:
> So, I'm porting Linux to our latest board... and I've got this pile of
> new code, and I'm itching to check it in somewhere. It's not perfect
> yet, but the board definately starts to come up, and the Symbios
> 53c875 driver can probe and identify devices on the SCSI bus.... so
> I'm thinking that I'm doing pretty well here.
>
> So, if I send this code as is, will it be accepted into the tree? Or
> do I have to wait until it's completely finished before I send it? I
> can see arguments either way, so I'm guessing it really comes down to
> Ralf's personal preferences...
I also take patches for partial support if I have confidence that the
support will be completed not too far after.
> P.S. Is there any way to get permission to make CVS commits, or should
> everything be done via Ralf? I've got another 2 designs behind this
> one which will all get Linux ported to them...
The intent is to move CVS to another machine in the near future. By
then I'll be able to generate accounts as I want but at this time it's
a pain to go through the SGI burocracy so I'm trying to avoid it.
Ralf
prev parent reply other threads:[~2002-02-21 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 1:38 Adding code to the tree Matthew Dharm
2002-02-21 1:51 ` Ralf Baechle [this message]
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=20020221025121.A29466@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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