On Fri, 31 Dec 1999, Wes Peters wrote:
> I have a good reason to revive this thread. I thought anyone who followed
> this conversation might want to know that one of the switches we dicussed,
> the Netgear FS-105, is on a special at CompUSA right now -- THROUGH TOMORROW.
> The special is a $20 m
> "Nate" == Nate Williams <[EMAIL PROTECTED]> writes:
Nate> find /local2/CVSfoo -name Root -print | fgrep CVS | perl -pi
Nate> -e 's#/local#/local2/#g;'
Perl? Bah! (I wrote this to also handle a rename of our CVS server. Adjust
as necessary.)
#!/bin/sh
for i in `find . -type d -nam
On Sun, Jan 09, 2000, Nate Williams wrote:
> find /local2/CVSfoo -name Root -print | fgrep CVS |
> perl -pi -e 's#/local#/local2/#g;'
^
Perhaps in this space you meant to type ``xargs''?
--
|Chris Costello <[EMAIL PROTECTED]>
|If you don't change your direction, you may end up w
> > > This has the side-effect(?) that all sources checked out from the 'old'
> > > repository location have references to /local/CVSfoo whereas cvs update
> > > obviously wants to have the references to /local2/CVSfoo.
> > The simplest way is to replace content of CVS/Root files. They
> > con
Wilko Bulte wrote:
> On Sun, Jan 09, 2000 at 10:27:16PM +0800, Peter Wemm wrote:
> > Ollivier Robert wrote:
> > > According to Wilko Bulte:
> > > > Is there any way, short of running a fresh cvs co, to correct this?
> > >
> > > *NOT TESTED*
> > >
> > > Something along the lines of
> > >
> > > p
On Sun, Jan 09, 2000 at 10:27:16PM +0800, Peter Wemm wrote:
> Ollivier Robert wrote:
> > According to Wilko Bulte:
> > > Is there any way, short of running a fresh cvs co, to correct this?
> >
> > *NOT TESTED*
> >
> > Something along the lines of
> >
> > perl -ni -e 's' **/{Root,Repository} (i
Ollivier Robert wrote:
> According to Wilko Bulte:
> > Is there any way, short of running a fresh cvs co, to correct this?
>
> *NOT TESTED*
>
> Something along the lines of
>
> perl -ni -e 's' **/{Root,Repository} (if using zsh)
>
> or
>
> find . \( -name Root -o -name Repository \) -path \
According to Wilko Bulte:
> Is there any way, short of running a fresh cvs co, to correct this?
*NOT TESTED*
Something along the lines of
perl -ni -e 's' **/{Root,Repository} (if using zsh)
or
find . \( -name Root -o -name Repository \) -path \*CVS\* | xargs perl -ni ...
if not.
--
Ollivi
Thus spake Boris Popov ([EMAIL PROTECTED]):
> > This has the side-effect(?) that all sources checked out from the 'old'
> > repository location have references to /local/CVSfoo whereas cvs update
> > obviously wants to have the references to /local2/CVSfoo.
> The simplest way is to replace
On Sun, 9 Jan 2000, Wilko Bulte wrote:
> In the course of reorganising my disks I moved my local CVS repository
> from /local/CVSfoo to /local2/CVSfoo
>
> This has the side-effect(?) that all sources checked out from the 'old'
> repository location have references to /local/CVSfoo whereas cvs up
On Sun, Jan 09, 2000 at 12:44:20PM +0100, Wilko Bulte wrote:
> In the course of reorganising my disks I moved my local CVS repository
> from /local/CVSfoo to /local2/CVSfoo
>
> This has the side-effect(?) that all sources checked out from the 'old'
> repository location have references to /local/
In the course of reorganising my disks I moved my local CVS repository
from /local/CVSfoo to /local2/CVSfoo
This has the side-effect(?) that all sources checked out from the 'old'
repository location have references to /local/CVSfoo whereas cvs update
obviously wants to have the references to /lo
12 matches
Mail list logo
