Hello,
We did our first release in SVN today. I used the copy command (shown
below) to copy from /trunk to /tag. Since not everything in /trunk was
needed for this release, I had to specify the directories which were
needed.
Q1. Is this the normal/correct way of doing things? For the new
> Hello,
>
> We did our first release in SVN today. I used the copy command (shown below)
> to copy from /trunk to /tag. Since not everything in /trunk was needed for
> this
> release, I had to specify the directories which were needed.
>
> Q1. Is this the normal/correct way of doing things? Fo
30, 2012 11:36 AM
To: Ahmed, Omair (GE Oil & Gas); users@subversion.apache.org
Subject: RE: SVN Tag / Branch question
> Hello,
>
> We did our first release in SVN today. I used the copy command (shown
> below) to copy from /trunk to /tag. Since not everything in /trunk
> was ne
On Tue, Oct 30, 2012 at 1:10 PM, Ahmed, Omair (GE Oil & Gas)
wrote:
>
> However, what's confusing is that when I copied the Docs directory from
> /trunk to /tags/release-1.6, the directory included files from the previous
> release also. Basically, I was expecting to see just the new files. I am
hat release version?"
>
>
> -Original Message-
> From: Bob Archer [mailto:bob.arc...@amsi.com]
> Sent: Tuesday, October 30, 2012 11:36 AM
> To: Ahmed, Omair (GE Oil & Gas); users@subversion.apache.org
> Subject: RE: SVN Tag / Branch question
>
>
> -Original Message-
> From: Bob Archer [mailto:bob.arc...@amsi.com]
> Sent: Tuesday, October 30, 2012 2:41 PM
> To: Ahmed, Omair (GE Oil & Gas); users@subversion.apache.org
> Subject: RE: SVN Tag / Branch question
>
> > You are correct in making the stat
l & Gas); users@subversion.apache.org
Subject: RE: SVN Tag / Branch question
> You are correct in making the statement below.
>
> However, what's confusing is that when I copied the Docs directory
> from /trunk to /tags/release-1.6, the directory included files from the
> previous release al
Guten Tag Ahmed, Omair (GE Oil & Gas),
am Freitag, 30. November 2012 um 00:49 schrieben Sie:
> Yes, we have cases where files (in the same path, i.e. trunk/docs)
> are intended for different releases. If as you say, we are doing
> something wrong, what's a better way to handle this?
> In /trunk/
