Matyas Selmeci wrote on Thu, Mar 15, 2012 at 13:48:03 -0500:
> Hi all,
>
> So apparently SVN 1.7 uses Sqlite to store working copy metadata. It
> also uses Sqlite to store repository metadata, but only if
> repo-sharing is enabled. Is that correct?
>
Yes, except that you mean "representation sha
Hi all,
So apparently SVN 1.7 uses Sqlite to store working copy metadata. It
also uses Sqlite to store repository metadata, but only if repo-sharing
is enabled. Is that correct?
In our department, we use AFS for network storage. We have both our
repository on it, and generally put our workin
Kind reader:
As far as I can tell, this does not apply to ISSUES 4099, 3609, or 2028, all of
which reference svn_uri_is_canonical.
The following URIs return TRUE from svn_uri_is_canonical:
1) file:///MyHost/path
2) file:///C:dir/path
3) file:///c=dir/path
I believe the prob
On Wed, Mar 14, 2012 at 5:15 PM, Daniel Shahaf wrote:
> Jason Wong wrote on Tue, Mar 13, 2012 at 06:57:59 -0700:
>> On Fri, Mar 2, 2012 at 8:12 AM, Daniel Shahaf wrote:
>> > Jason Wong wrote on Fri, Mar 02, 2012 at 07:32:38 -0800:
>> >> On Fri, Mar 2, 2012 at 2:58 AM, Daniel Shahaf wrote:
>> >>
On Thu, Mar 15, 2012 at 8:05 AM, Mark-E wrote:
>
> The section is setup like this in SVN:
>
> Archive/project1/trunk
> Archive/project2/trunk
> Archive/project3/trunk
>
> What I would like to be able to do is use svn co to check out the trunk
> folder for each project without specifically issuing
On Thu, Mar 15, 2012 at 05:40:23PM +0400, Konstantin Kolinko wrote:
> 1) do "svn co --depth immediates" for the repository root
> 2) and follow it by "svn up --set-depth" for the subfolders that you
> are interested in.
You can also use --depth empty in the first command to avoid having
all immedi
>That is not possible. But you may look into the "sparse checkout" feature.
>
>To set it up you can
>1) do "svn co --depth immediates" for the repository root
>2) and follow it by "svn up --set-depth" for the subfolders that you
>are interested in.
>
>If you are on Unixes then you can use wildcard
2012/3/15 Mark-E :
>
> I am using OpenGrok as a search engine for SVN.
>
> I have an Archived section of obsolete code that users still want to be able
> to search.
> It is currently not searchable in our grok installation.
>
> The section is setup like this in SVN:
>
> Archive/project1/trunk
> Arc
I am using OpenGrok as a search engine for SVN.
I have an Archived section of obsolete code that users still want to be able
to search.
It is currently not searchable in our grok installation.
The section is setup like this in SVN:
Archive/project1/trunk
Archive/project2/trunk
Archive/project
On Thu, 15 Mar 2012 02:06:08 +, Daniel Shahaf wrote:
> Andreas Krey wrote on Wed, Mar 14, 2012 at 15:33:35 +0100:
...
> > But the real strange thing: I did only do a merge; not actually
> > edit any properties myself.
> >
>
> So? Propchanges are merged too.
Yes, but they weren't modified (b
10 matches
Mail list logo