2010/11/12 Ryan Schmidt :
> On Nov 11, 2010, at 18:33, San Martino wrote:
>
>> $ svn mkdir file:///home/x/repo/tag/change001/
>> $ svn copy --parents file:///home/x/repo/trunk/test/java_imports
>> file:///home/x/repo/tag/change001/
>> $ svn ls file:///home/x/repo/tag/change001/
>> java_imports
>>
>
On Nov 11, 2010, at 18:33, San Martino wrote:
> $ svn mkdir file:///home/x/repo/tag/change001/
> $ svn copy --parents file:///home/x/repo/trunk/test/java_imports
> file:///home/x/repo/tag/change001/
> $ svn ls file:///home/x/repo/tag/change001/
> java_imports
>
> From the help "svn copy --parents
Hello Johan
2010/11/11 Johan Corveleyn :
> I think you can also make a tag or branch of a subset of files
> completely on the server (without the need to create a sparse working
> copy first). This can be done with the --parents option of "svn copy",
> and multiple SRC arguments (which can all be
On Thu, Nov 11, 2010 at 12:18 PM, San Martino wrote:
> 2010/11/11 Cooke, Mark :
>>> > > Database/
>>> > > Scripts/
>>> > > Packages/
>>> > > Application Server
>>> > > libs/
>>> > > servlets/
>>> > >
>>> > > while /tag and branch/ are empty
>>> > >
>>> > > There are hundreds of files under
On 11/10/2010 3:05 PM, San Martino wrote:
Hello Ryan,
Of course the cleanest way is to checkout the whole trunk/ and tag the
trunk each time.
A single checkout of the whole / directory is tens of GB over a
network (non-LAN), multiply this for all the deveopers.
But this should only have to h
On 11/11/2010 5:18 AM, San Martino wrote:
2010/11/11 Cooke, Mark:
Database/
Scripts/
Packages/
Application Server
libs/
servlets/
while /tag and branch/ are empty
There are hundreds of files under each directory. We want to
preserve this layout, since it's basically impossible to
r
On 11/11/2010 3:18 AM, San Martino wrote:
> How are tags really "cheaps"
> (time and space on disk) when the whole /trunk is measured in Gbs of
> data? Is there really a point to tag the whole /trunk when we just
> intended to make a change to a real project?
>
> thanks
http://svnbook.red-bean.c
It's a little late for you, but I've found that sometimes it is best
to start "clean" and give up your old history. Just keep your old
repository around if you need this information.
There are many times I've moved a group to Subversion, and we simply
copied over the end points of branches, and re
2010/11/11 Cooke, Mark :
>> > > Database/
>> > > Scripts/
>> > > Packages/
>> > > Application Server
>> > > libs/
>> > > servlets/
>> > >
>> > > while /tag and branch/ are empty
>> > >
>> > > There are hundreds of files under each directory. We want to
>> > > preserve this layout, since it'
ccoli; users@subversion.apache.org
> Cc: San Martino
> Subject: RE: Help or suggestions on porting to subversion
>
> > -Original Message-
> > From: Giulio Troccoli [mailto:giulio.trocc...@uk.linedata.com]
> > Sent: 11 November 2010 08:45
> > Subject: RE: Help or sugg
> -Original Message-
> From: Giulio Troccoli [mailto:giulio.trocc...@uk.linedata.com]
> Sent: 11 November 2010 08:45
> Subject: RE: Help or suggestions on porting to subversion
>
> [CUT]
>
> >
> > > The thing we want is:
> > > - checkout sing
[CUT]
>
> > The thing we want is:
> > - checkout single/scattered files from different directories
> > - modify/commit them
> > - group the files and tag this group (only the files in this group).
> >
> This is not AFAIK directly possible in subversion (or any
> other similar tool that I have used
t; > Or you could check out a sparse directory of only what you
> > need to work on.
> >
> > Or you could reorganize the files by project so that you
> > can check out each project. If there are hundreds of projects
> > and this is daunting, you could just convert projects
Hello Ryan,
Of course the cleanest way is to checkout the whole trunk/ and tag the
trunk each time.
A single checkout of the whole / directory is tens of GB over a
network (non-LAN), multiply this for all the deveopers.
The solution does not scale well even if checkout with --depth is
disabled. F
On Nov 10, 2010, at 14:09, San Martino wrote:
> we are porting hundreds of projects from an old versioning system to
> subversion. We would like to make use of the trunk, tag and branch
> concepts.
> For the convertion we used an automatic tool which preserved the
> original layout under trunk/ .
Hello,
we are porting hundreds of projects from an old versioning system to
subversion. We would like to make use of the trunk, tag and branch
concepts.
For the convertion we used an automatic tool which preserved the
original layout under trunk/ . By looking at the layout, one problem
is that the
16 matches
Mail list logo
