From: willy@thepuffingroup.com
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] CVS cleanups
Date: Tue, 23 May 2000 18:12:11 -0400 [thread overview]
Message-ID: <20000523181211.E17536@thepuffingroup.com> (raw)
In-Reply-To: <20000523180827.D17536@thepuffingroup.com>; from willy@thepuffingroup.com on Tue, May 23, 2000 at 06:08:27PM -0400
On Tue, May 23, 2000 at 06:08:27PM -0400, willy@thepuffingroup.com wrote:
>
> The following files have only their CVS id string changed in our CVS
> repo. Would anyone like to fix them before we do the 2.3.99-pre8 merge
> on Friday? I'm just going through now and preparing a list of files
> we'll need to pay attention to.
I really did just forget to attach the list of files, didn't I? This cold
is getting to me.
linux-2.3/Documentation/usb/error-codes.txt
linux-2.3/Documentation/usb/uhci.txt
linux-2.3/arch/sparc/lib/ashldi3.S
linux-2.3/arch/sparc64/kernel/iommu_common.c
linux-2.3/arch/sparc64/kernel/iommu_common.h
linux-2.3/arch/sparc64/prom/map.S
linux-2.3/drivers/i2c/i2c-pcf8584.h
linux-2.3/drivers/scsi/README.aha152x
linux-2.3/drivers/telephony/ixj.c
linux-2.3/drivers/telephony/ixj.h
linux-2.3/drivers/usb/plusb.c
linux-2.3/drivers/zorro/names.c
linux-2.3/fs/cramfs/inflate/adler32.c
linux-2.3/fs/cramfs/inflate/uncompr.c
linux-2.3/fs/cramfs/inflate/zconf.h
linux-2.3/fs/cramfs/inflate/zutil.h
linux-2.3/include/asm-m68k/apollodma.h
linux-2.3/include/asm-ppc/hw_irq.h
linux-2.3/include/linux/i2c-algo-bit.h
linux-2.3/include/linux/i2c-algo-pcf.h
linux-2.3/include/linux/i2c-dev.h
linux-2.3/include/linux/i2c-elektor.h
linux-2.3/include/linux/ixjuser.h
linux-2.3/include/net/inetpeer.h
linux-2.3/net/ipv4/inetpeer.c
prev parent reply other threads:[~2000-05-23 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-23 22:08 [parisc-linux] CVS cleanups willy
2000-05-23 22:12 ` willy [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=20000523181211.E17536@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.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.