All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ang <mang@subcarrier.org>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] cvs directory renaming - *action required*
Date: Sat, 23 Sep 2000 03:56:03 -0400	[thread overview]
Message-ID: <39CC6213.5B7DDC41@subcarrier.org> (raw)
In-Reply-To: 20000923150340.M21274@neep.com.au

Andrew Shugg wrote:
> 
> $ for i in $(find linux-2.3 binutils-2.10 -name Repository); do echo $(cat $i|sed 's/-[0-9.]*//') > $i; done

This is also incorrect since you'll replace any dashes that appear.  You
want this:
cd binutils-2.10
for z in `find . -name Repository`
do
  sed -e 's/-2.10//' $z > zzz && mv zzz $z
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?

Because "linux-2.3" is being renamed to "linux", so the old "linux" had
to go.  The stuff being moved is very old, and is being moved out of the
way to reduce the amount of cruft in the top level of the repository. 
This should be the last time we have to do this.  After the rename, no
new directories should be created unless absolutely necessary: branches
should be used instead.

	- Mike.

  reply	other threads:[~2000-09-23  7:54 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
2000-09-23  7:56   ` Michael Ang [this message]
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=39CC6213.5B7DDC41@subcarrier.org \
    --to=mang@subcarrier.org \
    --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.