Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of markphip@gmail.com designates
 209.85.219.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <6dd4da1c7e5f4a088f2dab506d14d907@DM2PR05MB797.namprd05.prod.outlook.com>
References: 
 <fe4db5e101bd4cd080e29b0e0e919ffb@DM2PR05MB797.namprd05.prod.outlook.com>
	<C07613594E445E4FBC779F202BC59EA03DC2C1FC96@DEMCHP99E84MSX.ww902.siemens.net>
	<6dd4da1c7e5f4a088f2dab506d14d907@DM2PR05MB797.namprd05.prod.outlook.com>
Date: Wed, 11 Dec 2013 10:57:49 -0500
Message-ID: 
 <CAHFaGCq2uca_B9+YQys6AXQtOPtozgXXMyXHvff7JZzRzzBQ2g@mail.gmail.com>
Subject: Re: Update-Only Checkout Enhancement
From: Mark Phippard <markphip@gmail.com>
To: Mark Kneisler <mark.kneisler@tceq.texas.gov>
Cc: "Cooke, Mark" <mark.cooke@siemens.com>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: multipart/alternative; boundary=089e013c6fa075760d04ed444ace

--089e013c6fa075760d04ed444ace
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Dec 11, 2013 at 10:46 AM, Mark Kneisler <
mark.kneisler@tceq.texas.gov> wrote:

> Yes, I understand the export function.  I want functionality for release
> management into test and production environments.
>
> For these environments I have a few requirements:
>         Files in these environments will NEVER be edited
>         For new releases I will need to perform an update to revision,
> which will add, update and delete needed files
>         I want as small of a .svn directory as possible
>
> I'm fairly certain that this functionality is currently not present, but I
> think there are many installations where this would be valuable.
>
> I'd like to create an enhancement request, but according to the website it
> was recommended that I post to this mailing list first.
>
>

Pristine files do not exist solely so you can edit files.  It is convenient
they exist so that you can diff your changes or revert your changes without
needing to contact the server, or even be online, but obviously those
commands could be made to use the server for that and simply require a
connection when no pristine is available.

The main reason the pristine files exist is so that the client and server
can exchange deltas with each other and minimize network traffic.  This is
just as true for update as it is for commit.  One of the original mantra's
for the 1.0 release was "disk is cheap, network is expensive".

There is an existing request in the system for making these files optional:

http://subversion.tigris.org/issues/show_bug.cgi?id=525

There is also an existing request for storing the pristine files in
compressed format:

http://subversion.tigris.org/issues/show_bug.cgi?id=908

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

--089e013c6fa075760d04ed444ace
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Dec 11, 2013 at 10:46 AM, Mark Kneisler <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mark.kneisler@tceq.texas.gov" target=3D"_blank">mark.kneisler@tc=
eq.texas.gov</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Yes, I understand the export function. =A0I want functiona=
lity for release management into test and production environments.<br>

<br>
For these environments I have a few requirements:<br>
=A0 =A0 =A0 =A0 Files in these environments will NEVER be edited<br>
=A0 =A0 =A0 =A0 For new releases I will need to perform an update to revisi=
on, which will add, update and delete needed files<br>
=A0 =A0 =A0 =A0 I want as small of a .svn directory as possible<br>
<br>
I&#39;m fairly certain that this functionality is currently not present, bu=
t I think there are many installations where this would be valuable.<br>
<br>
I&#39;d like to create an enhancement request, but according to the website=
 it was recommended that I post to this mailing list first.<br><br></blockq=
uote><div><br></div><div><br></div><div>Pristine files do not exist solely =
so you can edit files. =A0It is convenient they exist so that you can diff =
your changes or revert your changes without needing to contact the server, =
or even be online, but obviously those commands could be made to use the se=
rver for that and simply require a connection when no pristine is available=
.</div>
<div><br></div><div>The main reason the pristine files exist is so that the=
 client and server can exchange deltas with each other and minimize network=
 traffic. =A0This is just as true for update as it is for commit. =A0One of=
 the original mantra&#39;s for the 1.0 release was &quot;disk is cheap, net=
work is expensive&quot;.</div>
<div><br></div><div>There is an existing request in the system for making t=
hese files optional:</div><div><br></div><div><a href=3D"http://subversion.=
tigris.org/issues/show_bug.cgi?id=3D525">http://subversion.tigris.org/issue=
s/show_bug.cgi?id=3D525</a><br>
</div><div><br></div><div>There is also an existing request for storing the=
 pristine files in compressed format:</div><div><br></div><div><a href=3D"h=
ttp://subversion.tigris.org/issues/show_bug.cgi?id=3D908">http://subversion=
.tigris.org/issues/show_bug.cgi?id=3D908</a></div>
<div><br></div></div>-- <br>Thanks<br><br>Mark Phippard<br><a href=3D"http:=
//markphip.blogspot.com/">http://markphip.blogspot.com/</a>
</div></div>

--089e013c6fa075760d04ed444ace--