mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.52
Date: Mon, 16 Dec 2002 10:16:39 -0500	[thread overview]
Message-ID: <20021216151639.GQ504@hopper.phunnypharm.org> (raw)
In-Reply-To: <20021216102639.A27589@infradead.org>

On Mon, Dec 16, 2002 at 10:26:40AM +0000, Christoph Hellwig wrote:
> On Sun, Dec 15, 2002 at 07:34:09PM -0800, Linus Torvalds wrote:
> > Ben Collins <bcollins@debian.org>:
> >   o IEEE-1394/Firewire update
> 
> This merge looks fishy.  It seems to be yet another let's throw my CVS
> repo in merge and backs out Al's work yo get rid of lots of devfs crap.

Quit talking shit. I go through a lot of effort to merge in changes sent
to Linus' tree into the Linux1394 repo. I don't just dump changes for no
good reason.

How about pointing out some specifics? Maybe make my job easier by
getting me some patches directly. Trying to track two seperate source
tree's isn't as easy as you might think.


-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  parent reply	other threads:[~2002-12-16 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  3:34 Linus Torvalds
2002-12-16 10:26 ` Christoph Hellwig
2002-12-16 12:05   ` James H. Cloos Jr.
2002-12-16 15:16   ` Ben Collins [this message]
2002-12-16 16:36     ` Christoph Hellwig
2002-12-16 16:40       ` Ben Collins
2002-12-16 17:26     ` Linus Torvalds
2002-12-16 17:36       ` Ben Collins
2002-12-16 20:39       ` Larry McVoy
2002-12-16 20:54         ` Linus Torvalds
2002-12-16 13:53 ` Gerd Knorr
2002-12-16  9:45 ALESSANDRO.SUARDI

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=20021216151639.GQ504@hopper.phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®