From: Christoph Hellwig <hch@infradead.org>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA update 0.9.6
Date: Mon, 28 Jul 2003 14:23:06 +0100 [thread overview]
Message-ID: <20030728142306.A9127@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0307281451220.28950-100000@pnote.perex-int.cz>; from perex@suse.cz on Mon, Jul 28, 2003 at 03:17:24PM +0200
On Mon, Jul 28, 2003 at 03:17:24PM +0200, Jaroslav Kysela wrote:
> But the changesets are really great, so I am thinking to switch the ALSA
> repository from CVS to BK soon. It will help to propagate changes better.
Thanks, that would be a lot nicer. With cvsps or similar tools it should
be possible to do a CVS checking -> BK cset conversion, too. I did
something similar for a SGI-internal RCS-based SCM.
next prev parent reply other threads:[~2003-07-28 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:24 [PATCH] ALSA update 0.9.6 Jaroslav Kysela
2003-07-28 12:43 ` Christoph Hellwig
2003-07-28 13:17 ` Jaroslav Kysela
2003-07-28 13:23 ` Christoph Hellwig [this message]
2003-07-29 18:00 ` juan l.
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=20030728142306.A9127@infradead.org \
--to=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).