From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] cvs directory renaming - *action required*
Date: Sat, 23 Sep 2000 15:03:44 +0800 [thread overview]
Message-ID: <20000923150340.M21274@neep.com.au> (raw)
In-Reply-To: <39CBF956.4833E405@subcarrier.org>; from mang@subcarrier.org on Fri, Sep 22, 2000 at 08:29:10PM -0400
Michael Ang said:
> In order to reduce some of the confusion about which directory was
> active in the repository (did I want "binutils", "binutils-old", or
> "binutils-2.10"?) some of the directories in the repository will be
> renamed. This will be moderately painful, but it's better to do the
> painful thing now while we can still stamp out the old cruft.
>
> "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:
This file "binutils-2.10/gas/testsuite/gas/cris/CVS/Repository" doesn't
contain a full repository path - all the others are /home/cvs/... but
this one contains just the relative path. Not sure what this means, if
anything... Some of the Repository files in the linux-2.3 module have
the same sort of thing. *shrug* Anyone know? =)
> $ 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
$ for i in $(find linux-2.3 binutils-2.10 -name Repository); do echo $(cat $i|sed 's/-[0-9.]*//') > $i; done
> P.S. If out of archeological interest you're looking for the old {linux,
> binutils, binutils-old, egcs-old} directory, it's been moved under
> directory "obsolete". e.g. "cvs co obsolete/binutils-old".
Why do this? Why not just tag those two modules on Wednesday when you
make the change to the repository structure?
Andrew.
--
Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/
"Just remember Basil, there's always someone worse off than yourself."
"Oh, really? I'd like to meet him ... I could do with a good laugh."
[ Sybil and Basil Fawlty, "Fawlty Towers" ]
next prev parent reply other threads:[~2000-09-23 7:03 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
2000-09-23 7:03 ` Andrew Shugg [this message]
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=20000923150340.M21274@neep.com.au \
--to=andrew@neep.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