X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77E0A.39B77EFA@onstor-exch02.onstor.net>; Fri, 13 Apr 2007 13:27:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: please review
Date: Fri, 13 Apr 2007 13:27:58 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0221572D@onstor-exch02.onstor.net>
In-Reply-To: <20070413120157.07f8182b@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: please review
Thread-Index: Acd9/jZlJeiYqhL1QZaOuqDa18yiQQACyVUw
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Here is how to rename a file in perforce. What you are doing will delete
the perforce history of the old file and create two new ones:

Renaming Files
How do you rename a file?

In Perforce you rename a file by integrating the existing file into a
new file and deleting the existing one. For example, to rename foo to
bar in the ola directory:

=09
	cd ola
	p4 integ foo bar
	p4 delete foo
	p4 submit

This marks the head revision of foo as deleted. When anyone syncs to the
ola directory now, their workspace versions of foo will be deleted and
replaced with bar.

To see the complete change history of bar, including changes that
affected it when it was named foo, use the "-i" option:

=09
	p4 changes -i bar

If you forget what bar was originally called, you can always find out by
looking at the last lines output by:

=09
	p4 filelog bar

-----Original Message-----
From: Andy Sharp=20
Sent: Friday, April 13, 2007 12:02 PM
To: Larry Scheer
Subject: Re: please review

I'm not sure I did the right thing on this, but I wanted to rename it
to old_mdrive_fstab, and then after that was committed, add the new
version as a new file.  Which is what I was trying to explain with all
that stuff about the new file.  But reading it I guess it didn't make
much sense.

A rename appears as a delete and an add I think.

Hope that answers your question.

Cheers,

a


On Fri, 13 Apr 2007 10:57:38 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Just starting to look at this....
> I have one question about the change to openbsd/src/etc/Makefile.
> What happened to mdrive_install.sh? Is it deprecated? Was its
> functionality moved to src/etc/rc. (I have looked at the two files
> yet.) I just want to make sure this wasn't an unintentional delete.
>=20
> L.
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, April 12, 2007 11:20 PM
> To: Larry Scheer
> Subject: please review
>=20
> change 23496 client ripper
>=20
>=20
> let me know if you have any questions
>=20
> i included the code to refuse to upgrade to secondary flash w/ old
> layout
>=20
> there is another new file, openbsd/src/etc/mdrive_fstab that will be
> added after this changelist is committed.  it currently sits in that
> directory under the name new_mdrive_fstab.  it may also be there under
> it's real name but that's just so that 'make release' will work right
> so i could test it.
>=20
>=20
> Change 23496 by andys@ripper on 2007/04/10 18:25:58 *pending*
>=20
>         New flash_install.sh script and friends to support new CF
> layout.
>        =20
>         TED00018269 need to change master install scripts for new CF
> layout
>=20
> Affected files ...
>=20
> ... //depot/FB-DELOREAN/nfx-tree/Makefile#7 edit
> ... //depot/FB-DELOREAN/nfx-tree/Tools/flash_install.sh#1 add
> ... //depot/FB-DELOREAN/nfx-tree/Tools/flash_install_512.sh#1 delete
> ... //depot/FB-DELOREAN/nfx-tree/code/ssc-nfxsh/cmd_flash.c#9 edit
> ... //depot/FB-DELOREAN/nfx-tree/code/ssc-nfxsh/cmd_upgrade.c#14 edit
> ... //depot/FB-DELOREAN/openbsd/src/etc/Makefile#1 edit
> ... //depot/FB-DELOREAN/openbsd/src/etc/mdrive_fstab#1 delete
> ... //depot/FB-DELOREAN/openbsd/src/etc/old_mdrive_fstab#1 add
> ... //depot/FB-DELOREAN/openbsd/src/etc/rc#2 edit
