2010/11/12 Les Mikesell :
> In any case, as I tried to point out earlier and others have repeated, it
> doesn't matter if you copy to tags or not. The purpose of the tag is just
> to give you a human-friendly name that you can use for documentation or
> steps in your process. Even without explici
On 11/12/2010 8:24 AM, San Martino wrote:
To avoid network issues with full checkouts we think about
sparse-checkouts of what is really needed, in most of the cases it's
single files
You can do whatever works best for each client on the client side.
Someone who has good connectivity and works
On Friday 12 November 2010, San Martino wrote:
> Basically we need to test each commit from /tag while others proceed
> on /trunk. Before we used to lock - modify - TEST [- correct bugs]
> unlock. This really slows down the development because TEST is a long
> period while development needs to be v
Hi San,
On Fri, Nov 12, 2010 at 3:20 PM, San Martino wrote:
> 2010/11/12 Erik Huelsmann :
>>> Do you think Subversion scales well for the following case, where
>>> /trunk contains about 5000 files and its size is 500Mb
>>> development requires 10 commits per day, 2-3 files changed per commit
>>>
2010/11/12 Les Mikesell :
> On 11/12/10 7:57 AM, San Martino wrote:
>>
>> 2010/11/11 Les Mikesell:
>>>
>>> That's not wrong in the sense that it won't work for a small repository,
>>> but
>>> it is not an efficient way to use subversion where you are concerned
>>> about
>>> space or time usage on t
2010/11/12 Erik Huelsmann :
>> Do you think Subversion scales well for the following case, where
>> /trunk contains about 5000 files and its size is 500Mb
>> development requires 10 commits per day, 2-3 files changed per commit
>> on average.
>> Each commit is tagged (yes) from /trunk on the reposi
On 11/12/10 7:57 AM, San Martino wrote:
2010/11/11 Les Mikesell:
That's not wrong in the sense that it won't work for a small repository, but
it is not an efficient way to use subversion where you are concerned about
space or time usage on the client. Normally you would just check out
workspace
Hi San,
On Fri, Nov 12, 2010 at 2:57 PM, San Martino wrote:
> 2010/11/11 Les Mikesell :
>> That's not wrong in the sense that it won't work for a small repository, but
>> it is not an efficient way to use subversion where you are concerned about
>> space or time usage on the client. Normally you
2010/11/11 Les Mikesell :
> That's not wrong in the sense that it won't work for a small repository, but
> it is not an efficient way to use subversion where you are concerned about
> space or time usage on the client. Normally you would just check out
> workspaces of one or more locations where y
On 11/11/2010 8:48 AM, Thorsten Schöning wrote:
Guten Tag Les Mikesell,
am Donnerstag, 11. November 2010 um 14:37 schrieben Sie:
Doesn't the client understand the file history if you 'svn switch' to the tag
path in a working copy and just get the differences, if any?
OK, maybe I'm wrong, beca
On Thursday 11 November 2010, Thorsten Schöning wrote:
> am Donnerstag, 11. November 2010 um 14:37 schrieben Sie:
> > Doesn't the client understand the file history if you 'svn switch' to the
> > tag path in a working copy and just get the differences, if any?
If you use switch, it will only trans
Guten Tag Les Mikesell,
am Donnerstag, 11. November 2010 um 14:37 schrieben Sie:
> Doesn't the client understand the file history if you 'svn switch' to the tag
> path in a working copy and just get the differences, if any?
OK, maybe I'm wrong, because I don't use svn switch but always use
comple
> I would like to know how tags and branches are "cheap copy" in terms
> of time and space.
>
> Since we can't reorganize the layout, we will need to tag big
> directories (about 500 Mb) even if we just sparse-chechkout single
> files.
> This operation might be done up to 10 times per day.
> Is thi
On 11/11/10 4:16 AM, San Martino wrote:
Hello,
I would like to know how tags and branches are "cheap copy" in terms
of time and space.
Since we can't reorganize the layout, we will need to tag big
directories (about 500 Mb) even if we just sparse-chechkout single
files.
This operation might be
On 11/11/10 5:57 AM, Thorsten Schöning wrote:
Guten Tag San Martino,
am Donnerstag, 11. November 2010 um 11:16 schrieben Sie:
Since we can't reorganize the layout, we will need to tag big
directories (about 500 Mb) even if we just sparse-chechkout single
files.
This operation might be done up t
Guten Tag San Martino,
am Donnerstag, 11. November 2010 um 11:16 schrieben Sie:
> Since we can't reorganize the layout, we will need to tag big
> directories (about 500 Mb) even if we just sparse-chechkout single
> files.
> This operation might be done up to 10 times per day.
> Is this operation r
Hello,
I would like to know how tags and branches are "cheap copy" in terms
of time and space.
Since we can't reorganize the layout, we will need to tag big
directories (about 500 Mb) even if we just sparse-chechkout single
files.
This operation might be done up to 10 times per day.
Is this opera
17 matches
Mail list logo
