From: Christoph Hellwig <hch@infradead.org>
To: Pat Gefre <pfg@sgi.com>
Cc: linux-ia64@vger.kernel.org, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code re-org
Date: Thu, 22 Jul 2004 17:55:14 +0000 [thread overview]
Message-ID: <20040722175514.GA15391@infradead.org> (raw)
In-Reply-To: <200407221514.i6MFEVag084696@fsgi900.americas.sgi.com>
On Thu, Jul 22, 2004 at 10:14:31AM -0500, Pat Gefre wrote:
> The code is organized in the following manner:
>
> diffs_of_common_c_files - this has the diffs of 'C' files that were changed
> but not renamed.
> diffs_of_common_h_files - this has the diffs of include files that were changed
> but not renamed.
> diffs_of_renamed_files - this has the diffs of all files that were renamed.
>
>
> source_code.tar.gz - tarball of new source files.
> Source_code_tree/ - directory of new source files.
I haven't looked at the code yet (and won't until I'm back from OLS), but
for sure thats not how we will merge the code. Please split it into small,
self-contained patches that do one thing each.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Pat Gefre <pfg@sgi.com>
Cc: linux-ia64@vger.kernel.org, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code re-org
Date: Thu, 22 Jul 2004 18:55:14 +0100 [thread overview]
Message-ID: <20040722175514.GA15391@infradead.org> (raw)
In-Reply-To: <200407221514.i6MFEVag084696@fsgi900.americas.sgi.com>
On Thu, Jul 22, 2004 at 10:14:31AM -0500, Pat Gefre wrote:
> The code is organized in the following manner:
>
> diffs_of_common_c_files - this has the diffs of 'C' files that were changed
> but not renamed.
> diffs_of_common_h_files - this has the diffs of include files that were changed
> but not renamed.
> diffs_of_renamed_files - this has the diffs of all files that were renamed.
>
>
> source_code.tar.gz - tarball of new source files.
> Source_code_tree/ - directory of new source files.
I haven't looked at the code yet (and won't until I'm back from OLS), but
for sure thats not how we will merge the code. Please split it into small,
self-contained patches that do one thing each.
next prev parent reply other threads:[~2004-07-22 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:14 Altix I/O code re-org Pat Gefre
2004-07-22 15:14 ` Pat Gefre
2004-07-22 17:55 ` Christoph Hellwig [this message]
2004-07-22 17:55 ` Christoph Hellwig
2004-07-22 17:57 ` Jesse Barnes
2004-07-22 17:57 ` Jesse Barnes
2004-07-22 19:20 ` Robin Holt
2004-07-22 19:20 ` Robin Holt
2004-07-22 19:40 ` Robin Holt
2004-07-22 19:40 ` Robin Holt
2004-07-22 19:42 ` Christoph Hellwig
2004-07-22 19:42 ` Christoph Hellwig
2004-07-22 20:20 ` Robin Holt
2004-07-22 20:20 ` Robin Holt
2004-07-22 20:29 ` Robin Holt
2004-07-22 20:29 ` Robin Holt
2004-07-22 20:52 ` Robin Holt
2004-07-22 20:52 ` Robin Holt
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=20040722175514.GA15391@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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 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.