From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA update [10/10] - 2002/08/05
Date: Tue, 01 Oct 2002 16:18:10 -0700 (PDT) [thread overview]
Message-ID: <20021001.161810.40456340.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210011607200.18575-100000@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Tue, 1 Oct 2002 16:22:33 -0700 (PDT)
Talk to David about the problems with an external CVS tree, he had many of
the same problems with his sparc/networking tree a long time ago. David,
maybe you can talk about how you solved them.
I basically tried to send patches on a daily basis.
If that failed... then I ended up with this huge diff
that I had to pick apart by hand like Alan does when merging
-ac bits.
Then I started to use bitkeeper, and I didn't have to go
through the pain of importing a new set of 2.5.x vanilla
changes before a merge.
prev parent reply other threads:[~2002-10-01 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 19:02 [PATCH] ALSA update [10/10] - 2002/08/05 Jaroslav Kysela
2002-09-30 0:56 ` David S. Miller
2002-09-30 16:20 ` Jaroslav Kysela
2002-09-30 20:52 ` David S. Miller
2002-09-30 21:29 ` Jaroslav Kysela
2002-09-30 21:41 ` David S. Miller
2002-10-01 23:22 ` Linus Torvalds
2002-10-01 23:18 ` David S. Miller [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=20021001.161810.40456340.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--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 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.