From: Michael Ang <mang@subcarrier.org>
To: Alan Modra <alan@linuxcare.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] cvs directory renaming - *action required*
Date: Fri, 22 Sep 2000 20:57:56 -0400 [thread overview]
Message-ID: <39CC0014.44712E59@subcarrier.org> (raw)
In-Reply-To: Pine.LNX.4.21.0009231139030.31535-100000@front.linuxcare.com.au
No, what I gave will not work and is in fact *horribly wrong*. I would
recommend that people use Alan's script fragment instead ;)
- Mike.
Alan Modra wrote:
>
> On Fri, 22 Sep 2000, Michael Ang wrote:
>
> > "linux-2.3" will be renamed to "linux"
> > "binutils-2.10" will be renamed to "binutils"
> >
> > If you currently have a tree checked out, you will need to change all of
> > your CVS/Repository files to point to the new directory names. With
> > bash you can do it like this:
> > $ cd linux-2.3
> > $ for i in `find . -name Repository`; do echo "linux" > $i; done
> > $ cd binutils-2.10
> > $ for i in `find . -name Repository`; do echo "binutils" > $i; done
>
> Errm, will this work? My linux-2.3/CVS/Repository file looks like this:
> /home/cvs/parisc/linux-2.3
> and linux-2.3/CVS/arch/Repository has
> /home/cvs/parisc/linux-2.3/arch
>
> I wasn't game to try the above, and instead used
>
> cd linux-2.3
> for z in `find . -name Repository`
> do
> sed -e 's/-2.3//' $z > zzz && mv zzz $z
> done
>
> with a simliar trick for binutils.
>
> --
> Linuxcare. Support for the Revolution.
next prev parent reply other threads:[~2000-09-23 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-23 0:29 [parisc-linux] cvs directory renaming - *action required* Michael Ang
2000-09-23 0:47 ` Alan Modra
2000-09-23 0:57 ` Michael Ang [this message]
2000-09-23 7:03 ` Andrew Shugg
2000-09-23 7:56 ` Michael Ang
2000-09-23 7:29 ` Andrew Shugg
2000-09-23 8:05 ` Michael Ang
2000-09-23 9:54 ` Andrew Shugg
2000-09-23 17:26 ` Matthew Wilcox
2000-09-25 17:22 ` Erik Paulson
2000-09-25 17:57 ` Michael Ang
2000-09-27 1:17 ` Matthew Wilcox
2000-09-27 1:29 ` Matt Taggart
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=39CC0014.44712E59@subcarrier.org \
--to=mang@subcarrier.org \
--cc=alan@linuxcare.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox