Crast, Nicholas wrote on Mon, Jan 25, 2016 at 14:16:52 +:
> For anyone else in the future, there is more information here:
> https://people.apache.org/~brane/svndocs/capi/group__Commit.html
Not quite. That's trunk's documentation; promises made there are not
binding. The released docs are th
: 315-445-5703
Email: nicholas.cr...@saabsensis.com
-Original Message-
From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Sent: Saturday, January 23, 2016 7:00 PM
To: Crast, Nicholas
Cc: users@subversion.apache.org
Subject: Re: Modifying SVN Externals with Specific Revision
Crast
Crast, Nicholas wrote on Wed, Jan 20, 2016 at 21:05:51 +:
> This is, in fact, the behavior I want. I just want to know if it's
> guaranteed that modifications to external directories with a specific
> revisions will not be committed.
It is an explicit API promise of svn_client_commit6():
* I
Hi all,
I have a folder with the svn:externals property set, grabbing an external
folder from a different part of the repository:
-r6367 ../common/testproc proc1/common
If I go into proc1/common and edit a file in there, svn stat shows the file as
modified, but it seems that since I specified a
" mechanism
>>> underneath, while dir externals are essentially an embedded checkout
>>> with some sugar on top).
>>>
>>> So, concerning to the problem of the OP:
>>>
>>>> From: "Hutchinson, Steve (UK)"
>>>> To: &
tion is entirely different
>> from directory externals (file externals use the "switch" mechanism
>> underneath, while dir externals are essentially an embedded checkout
>> with some sugar on top).
>>
>> So, concerning to the problem of the OP:
>>
>>&
als are essentially an embedded checkout
> with some sugar on top).
>
> So, concerning to the problem of the OP:
>
>> From: "Hutchinson, Steve (UK)"
>> To: "users@subversion.apache.org"
>> Sent: Wednesday, May 1, 2013 7:01 AM
>> Subject: SVN Ext
> To: "users@subversion.apache.org"
> Sent: Wednesday, May 1, 2013 7:01 AM
> Subject: SVN Externals 1.6 to 1.7 migration issue
>
> Hi,
>
> We're been using 1.6 svn externals to manage a FW task.
>
> In the repository we have a folder structure (which is
___
> From: "Hutchinson, Steve (UK)"
>To: "users@subversion.apache.org"
>Sent: Wednesday, May 1, 2013 7:01 AM
>Subject: SVN Externals 1.6 to 1.7 migration issue
>
>
>Hi,
>
>We're been using 1.6 svn externals to manage a FW tas
Hi,
We're been using 1.6 svn externals to manage a FW task.
In the repository we have a folder structure (which is pretty much defined by
the tools we are using) as below :-
FOLDER A -> file_a1.txt, file_a2.txt, file_a3.txt
FOLDER B -> file_b1.txt, file_b2.txt, file_b3.txt
On 20/03/12 23:58, Philip Martin wrote:
Matthew J Fletcher writes:
I've been expermenting with SVN externals and found an issue which i
dont fully understand. My repository is as follows;
--
+Play (with and extern to URL "https://swserver:8443/svn/Play/Shared
Sour
Matthew J Fletcher writes:
> I've been expermenting with SVN externals and found an issue which i
> dont fully understand. My repository is as follows;
>
>
> --
>
> +Play (with and extern to URL "https://swserver:8443/svn/Play/Shared
&
On 13/03/12 18:07, Matthew J Fletcher wrote:
Hi,
I've been expermenting with SVN externals and found an issue which i
dont fully understand. My repository is as follows;
--
+Play (with and extern to URL "https://swserver:8443/svn/Play/Shared
Sources" Local
Hi,
I've been expermenting with SVN externals and found an issue which i
dont fully understand. My repository is as follows;
--
+Play (with and extern to URL "https://swserver:8443/svn/Play/Shared
Sources" Local Path "Project 3")
- Project 3
On Jul 29, 2011, at 8:17 AM, Thomas Harold wrote:
> http://subversion.apache.org/docs/release-notes/1.5.html#externals
>
> The relative URLs being allowed in svn:externals was a huge step forward.
> But it still relies on the source path not ever changing.
>
> For example:
>
> /repos/zag foo
http://subversion.apache.org/docs/release-notes/1.5.html#externals
The relative URLs being allowed in svn:externals was a huge step
forward. But it still relies on the source path not ever changing.
For example:
/repos/zag foo/bar1
Which is fine as long as "zag" never changes its name.
Wha
On Feb 14, 2011, at 02:06, Stephen Connolly wrote:
> On 14 Feb 2011 07:59, Ryan Schmidt wrote:
> >
> > On Feb 14, 2011, at 01:57, Stephen Connolly wrote:
> >
> >> yeah, but you'd want at least an option for the client to override ;-)
> >
> > Why would one want that?
>
> because you might not w
because you might not want the git on the system path
because you may not have permissions on windows to set the uri handler
just two, there's more
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype
On Feb 14, 2011, at 01:57, Stephen Connolly wrote:
> yeah, but you'd want at least an option for the client to override ;-)
Why would one want that?
yeah, but you'd want at least an option for the client to override ;-)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 14 Feb 2011 07:12, "Ryan Schmidt"
wrote:
On Feb 12, 2011, at 13:26, Stephen Connolly wrote:
> oh I like that.
>
> you could even allow the client config file to add custom uri schemes and the
> path to the exec that handles them
Well, I wasn't thinking there would be any client-side configuration
possibility. I merely meant that the
oh I like that.
you could even allow the client config file to add custom uri schemes and
the path to the exec that handles them
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
scree
On Feb 12, 2011, at 00:25, Robert Bielik wrote:
> Ryan Schmidt skrev 2011-02-11 22:20:
>>
>
>> svn:externals is for accessing other (or the same) Subversion repositories
>> only.
>
> Yes, I know, but I had hopes :) Wouldn't it be cool with a svn:command
> feature in which you'd be able to wri
Ryan Schmidt skrev 2011-02-11 22:20:
On Feb 11, 2011, at 08:28, Robert Bielik wrote:
In my project I need to use a library that's only available using git, I wonder
if there is some way to have svn:externals point to
a git repo (just doing a "git pull") ?
svn:externals is for accessing othe
On Feb 11, 2011, at 08:28, Robert Bielik wrote:
> In my project I need to use a library that's only available using git, I
> wonder if there is some way to have svn:externals point to
> a git repo (just doing a "git pull") ?
svn:externals is for accessing other (or the same) Subversion reposito
Hi all,
In my project I need to use a library that's only available using git, I wonder
if there is some way to have svn:externals point to
a git repo (just doing a "git pull") ?
TIA
/Rob
Hi group,
We have a product development structure that looks a bit like below :-
trunk
Design
Module_A
file_bundle_x_source
Module_B
file_bundle_y_source
Verification - (externals)
Simulation_1
file_bundle_x
Simulation_2
file_b
Stefan,
Your point well understood now. Thanks for the clarification,
appreciated.
Steve H
-Original Message-
From: Stefan Sperling [mailto:s...@elego.de]
Sent: 08 November 2010 17:01
To: Hutchinson, Steve (UK)
Cc: users@subversion.apache.org
Subject: Re: Svn externals question
On Mon, Nov 08, 2010 at 10:24:03AM -, Hutchinson, Steve (UK) wrote:
> >Do it the other way: Store your component configuration in a versioned
> >file or even a database, and write a script to configure svn:externals
> >properties based on that data. Maybe even add an automated check into
> >the
Hi
>The designers of the externals feature envisioned maybe a handful of
external library dependencies that don't vary much over time.
>These are automatically pulled into a working copy, much like an
automated svn checkout.
>But the design doesn't account for what happens when people start using
use another answer to continue that thread.
Regards
Steve H
-Original Message-
From: David Weintraub [mailto:qazw...@gmail.com]
Sent: 05 November 2010 16:17
To: Hutchinson, Steve (UK)
Cc: users@subversion.apache.org
Subject: Re: Svn externals question
>>>>> SPECIAL MBD
On Nov 5, 2010, at 11:54, David Weintraub wrote:
> The big problem with svn:externals is that they don't version very well.
> The problem is that the external directories themselves aren't tagged
> or branched when I did my tag or branch
If this is important to you, then you should use the svnco
On Fri, Nov 5, 2010 at 10:09 AM, Stefan Sperling wrote:
> The designers of the externals feature envisioned maybe a handful
> of external library dependencies that don't vary much over time.
> These are automatically pulled into a working copy, much like an automated
> svn checkout.
>
> But the de
On Fri, Nov 5, 2010 at 9:49 AM, Hutchinson, Steve (UK)
wrote:
> Is there a simple way of identifying in a structure folders that have
> external properties, come to think of it maybe any form of property ?
Not 100% clear what you're looking for. You could be looking for one
of two things:
1). Yo
On Fri, Nov 5, 2010 at 3:09 PM, Stefan Sperling wrote:
> On Fri, Nov 05, 2010 at 01:49:03PM -, Hutchinson, Steve (UK) wrote:
>> Hi,
>>
>> Currently we are attempting to use svn externals to help build various
>> projects from what I would call a few "reuse&quo
On Fri, Nov 05, 2010 at 11:03:58AM -0400, Jack Repenning wrote:
> If you do switch to the approach Stefan suggests (and I agree, it's
> probably more satisfactory) you also might want to use "svn switch"
> instead of the svn:externals. You'll still have the auditable,
> versioned definition of your
ipt), but also there will be
more freedom for variations, such as while preparing a new configuration.
Sent from my iPhone
On Nov 5, 2010, at 10:09 AM, "Stefan Sperling" wrote:
> On Fri, Nov 05, 2010 at 01:49:03PM -, Hutchinson, Steve (UK) wrote:
>> Hi,
>>
>&g
On Fri, Nov 05, 2010 at 01:49:03PM -, Hutchinson, Steve (UK) wrote:
> Hi,
>
> Currently we are attempting to use svn externals to help build various
> projects from what I would call a few "reuse" repositories. We are
> attempting to be "structured" as t
ne
On Nov 5, 2010, at 9:50 AM, "Hutchinson, Steve (UK)"
wrote:
> Hi,
>
> Currently we are attempting to use svn externals to help build various
> projects from what I would call a few "reuse" repositories. We are attempting
> to be "structured" as to what
Hi,
Currently we are attempting to use svn externals to help build various
projects from what I would call a few "reuse" repositories. We are
attempting to be "structured" as to what level of design hierarchy we
apply the properties but sometimes when we inherit a design pe
Hi
We have a repo with lots of svn:externals that looks like this
^tags/x/y z
Each time one executes a svn up or svn status it takes a very long time
to complete. The reason is that for each such external a new svnserve if
started on the server.
The ^tags/x/y externals are relative to the repo s
41 matches
Mail list logo
