> Thanks Andy. We really want to work with a file version, or revision, as
> opposed to a tree revision. Suppose there are three revisions of File-1
> in the repository and one revision of File-2.
>
> File-1 revision 63
> File-1 revision 64
> File-2 revision 65
> File-1 revision 66
>
> Suppose
On Thu, Jan 14, 2010 at 11:30, Headley, Ronald (PSC/ISMS/EAD-CTR)
wrote:
> Thanks Andy. We really want to work with a file version, or revision, as
> opposed to a tree revision. Suppose there are three revisions of File-1 in
> the repository and one revision of File-2.
>
> File-1 revision 63
S/EAD-CTR)
Cc: users@subversion.apache.org
Subject: Re: Verifying a file version
On Wed, Jan 13, 2010 at 17:02, Headley, Ronald (PSC/ISMS/EAD-CTR)
wrote:
> Good evening.
>
>
>
> We recently encountered an issue where an incorrect version, or more
> specifically, a non-exist
S/PSC/ISMS/ESS PMO (Program Management Office)
(a SDVOSB)
301-525-3801 (cell)
-Original Message-
From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
Sent: Wednesday, January 13, 2010 6:24 PM
To: Headley, Ronald (PSC/ISMS/EAD-CTR)
Cc: users@subversion.apache.org
Subject: Re: Verify
On Wed, Jan 13, 2010 at 17:02, Headley, Ronald (PSC/ISMS/EAD-CTR)
wrote:
> Good evening.
>
>
>
> We recently encountered an issue where an incorrect version, or more
> specifically, a non-existing version, of a file was promoted to production.
> We want to enhance our process to ensure we, at a mi
On Jan 13, 2010, at 16:02, Headley, Ronald (PSC/ISMS/EAD-CTR) wrote:
> We recently encountered an issue where an incorrect version, or more
> specifically, a non-existing version, of a file was promoted to production.
> We want to enhance our process to ensure we, at a minimal, export an exist
Good evening.
We recently encountered an issue where an incorrect version, or more
specifically, a non-existing version, of a file was promoted to
production. We want to enhance our process to ensure we, at a minimal,
export an existing version of a file. Can anyone suggest a command that
wil
