Hello ,
I have externals from other repo's configured in my master project under trunk.
When I tag the trunk and then checkout the tag, the externals are not checked
out.
When I tag the entire repo and then checkout the tag, the externals are checked
out. Is this the normal behavior? [I tried fr
Hello,
I have a SVN Master-Slave setup,
The slave repo gets updated through svnsync process,
but while observing the sync process I figured out that the Integration
branch is not getting the the updates from its Master branch.
please help me on this issue
Thanks,
Suhas Malusare
Guten Tag suhas malusare,
am Donnerstag, 1. März 2012 um 10:08 schrieben Sie:
> I have a SVN Master-Slave setup,
> The slave repo gets updated through svnsync process,
> but while observing the sync process I figured out that the Integration
> branch is not getting the the updates from its Master
4073 says this is supposed to have been fixed. I'm now on 1.7.5 and still
have the same issue.
I can't use a relative path cos that is not where the libray is. I need
absolute because some apps (viz VS 2010) require absolute paths for library
references.
I have to put the libraries on the C dr
Hi All,
I am trying to build/install subversion 1.7.3 on
rhe4-x86_64 platform, I come across with below error and I could able to
move further..
~/subv/subversion/libsvn_repos/.libs/libsvn_repos-1.so.0: undefined reference
to `svn_txdelta_to_svndiff2'
~/subv/subversion/libsvn_ra/.libs/libsvn_
On Thu, Mar 01, 2012 at 03:08:55AM -0800, coolie wrote:
> 4073 says this is supposed to have been fixed. I'm now on 1.7.5 and still
> have the same issue.
>
> I can't use a relative path cos that is not where the libray is. I need
> absolute because some apps (viz VS 2010) require absolute paths
Stefan Sperling writes:
> On Thu, Mar 01, 2012 at 03:08:55AM -0800, coolie wrote:
>> 4073 says this is supposed to have been fixed. I'm now on 1.7.5 and still
>> have the same issue.
>>
>> I can't use a relative path cos that is not where the libray is. I need
>> absolute because some apps (vi
On Thu, Mar 01, 2012 at 01:04:04PM +0100, Stefan Sperling wrote:
> On Thu, Mar 01, 2012 at 03:08:55AM -0800, coolie wrote:
> > 4073 says this is supposed to have been fixed. I'm now on 1.7.5 and still
> > have the same issue.
> >
> > I can't use a relative path cos that is not where the libray is
On Thu, Mar 01, 2012 at 01:01:23PM +, Philip Martin wrote:
> The 4073 fix doesn't allow absolute paths with drive letters. It merely
> prevents the assertion by extending the checking so that paths with
> drive letters are treated as absolute and skipped.
Yes, I just realised that while revie
Stefan Sperling writes:
> Currently, externals definitions cannot point to absolute paths.
> This might be fixed in the future, once multiple working copies
> can share a single .svn directory.
Perhaps, but perhaps not. Allowing svn:externals to modify paths
outside a working copy has security
On Wed, Feb 29, 2012 at 4:14 PM, Justin Johnson wrote:
> On Wed, Feb 29, 2012 at 11:22 AM, Daniel Shahaf wrote:
>
>> Justin Johnson wrote on Wed, Feb 29, 2012 at 11:11:18 -0600:
>> > On Wed, Feb 29, 2012 at 10:35 AM, Daniel Shahaf
>> wrote:
>> >
>> > > Justin Johnson wrote on Wed, Feb 29, 2012 a
>
> > > > > - Are the failing revisions always small (eg: just a URL-URL copy),
>>> > > > > or always large (eg: results of a merge)?
>>> > > > >
>>> > > > >
>>> > > > As mentioned before, so far it appears to be 1) create a tag by
>>> copying
>>> > > an
>>> > > > entire working copy of a branch t
Justin Johnson wrote on Thu, Mar 01, 2012 at 08:28:20 -0600:
> To make sure I understand the issue, should I be concerned about the
> repositories and our ability to reproduce the history or recover from any
> corruption that this bug may have caused?
The only known (and predicted) effect of the e
On Mar 1, 2012, at 02:59, Neson Maxmelbin (RBEI/EMT4) wrote:
> I have externals from other repo's configured in my master project under
> trunk.
> When I tag the trunk and then checkout the tag, the externals are not checked
> out.
> When I tag the entire repo and then checkout the tag, the ext
Hello,
I'm currently learning SVN as we're planning to use it here in the near future.
Some of our projects are structured like this (MS Windows):
D:\Source\Project1
D:\Source\Project2
D:\Source\CommomLibraries
Where Project1 and Project2 are individual projects but both rely on files
which resi
On Thu, Mar 01, 2012 at 04:35:32PM +0100, Humm, Markus wrote:
> Hello,
>
> I'm currently learning SVN as we're planning to use it here in the near
> future.
> Some of our projects are structured like this (MS Windows):
>
> D:\Source\Project1
> D:\Source\Project2
> D:\Source\CommomLibraries
>
>
Hi,
Having
to develop two distinct, un-related Projects, I wonder whether it is
sensible to store them both into a unique Subversion Repository, or it is
natural to create two distinct Repositories, each one dedicated to a
unique Project.
In
other words, a Subversion Repository is natu
> -Original Message-
> From: Pietro Moras [mailto:studio...@hotmail.com]
> Sent: 01 March 2012 16:47
> Subject: Subversion Repository: naturally a single- or
> multi-Project versioning storage?
>
> Hi,
>
> Having to develop two distinct, un-related Projects, I
> wonder whether it i
On Thu, Mar 1, 2012 at 10:47 AM, Pietro Moras wrote:
> Hi,
>
> Having to develop two distinct, un-related Projects, I wonder whether it
> is sensible to store them both into a unique Subversion Repository, or it is
> natural to create two distinct Repositories, each one dedicated to a unique
>
On Mar 1, 2012, at 10:47, Pietro Moras wrote:
> Having to develop two distinct, un-related Projects, I wonder whether it
> is sensible to store them both into a unique Subversion Repository, or it is
> natural to create two distinct Repositories, each one dedicated to a unique
> Project.
>
On Tue, Feb 28, 2012 at 1:07 AM, Daniel Shahaf wrote:
> Jason Wong wrote on Mon, Feb 27, 2012 at 07:36:39 -0800:
>> On Thu, Feb 16, 2012 at 12:14 PM, Daniel Shahaf wrote:
>>
>> >
>> > The output from these two tells me two things:
>> >
>> > 1. The minfo-cnt value is reasonable (within a typical b
Hi,
For some time now we've been lumping projects together in the same
repository and serving them up using apache. So our repository at
/svn_data/data will look like this
/
/project_A
/trunk
/branches
/tags
/project_B
/trunk
/branches
/tags
...
"Ravish Nayak S. R." writes:
> I am trying to build/install subversion 1.7.3 on
> rhe4-x86_64 platform, I come across with below error and I could able to
> move further..
>
> ~/subv/subversion/libsvn_repos/.libs/libsvn_repos-1.so.0: undefined reference
> to `svn_txdelta_to_svndiff2'
>
> ~/sub
On Mar 1, 2012, at 15:46, Mattius McLaughlin wrote:
> I'd like to break each of those projects into separate repositories. Given
> the number of designers we have, it's a bit unreasonable to expect everyone
> to recreate every workspace so I'd like to keep all URLs the same.
There's no choice
24 matches
Mail list logo
