On 30/04/2013 09:52, Philip Martin wrote:
If built with SASL support then svnserve always initialises the SASL
subsystem. This must be done if SASL is to be available and at this
stage the server doesn't know which repositories will be accessed.
It appears to be the SASL libraries that are pro
This is precisely what we are looking for. For the most part, we distribute
a new executable for each update, so an overwrite is all we care about.
The main reason we are moving to SVN is because the current deployment
process uses a fileshare where updates are pushed out to. At least with
SVN, we
> I don't understand why I can't simply over-write the existing file in
the
> directory? On many occasions, a build may only result in one new
executable.
> To have to delete/rename the entire directory seems like overkill.
While it kinda defeats the purpose of Subversion, you can use the svnmuc
On Fri, May 3, 2013 at 11:59 AM, C M wrote:
> I don't understand why I can't simply over-write the existing file in the
> directory? On many occasions, a build may only result in one new executable.
> To have to delete/rename the entire directory seems like overkill.
Converting the initial import
Guten Tag C M,
am Freitag, 3. Mai 2013 um 18:59 schrieben Sie:
> I don't understand why I can't simply over-write the existing file
> in the directory? On many occasions, a build may only result in one
> new executable. To have to delete/rename the entire directory seems like
> overkill.
Deletio
I don't understand why I can't simply over-write the existing file in the
directory? On many occasions, a build may only result in one new
executable. To have to delete/rename the entire directory seems like
overkill.
And for the most part, we only have one top level directory below which all
the
C. Michael Pilato wrote on Fri, May 03, 2013 at 09:34:16 -0400:
> In Subversion, your file's contents are considered sacred. Unless you set
> the svn:eol-style property on a given file, well-behaved Subversion clients
> will not attempt to perform newline translation on that file.
I would state t
Les Mikesell wrote on Fri, May 03, 2013 at 11:44:53 -0500:
> On Fri, May 3, 2013 at 11:23 AM, C M wrote:
> > We plan to use a SVN repository as a deployment mechanism so technicians can
> > download and install the application binaries for a customer system.
> >
> > The directory where we want the
On Fri, May 3, 2013 at 11:23 AM, C M wrote:
> We plan to use a SVN repository as a deployment mechanism so technicians can
> download and install the application binaries for a customer system.
>
> The directory where we want them to download from will always have the
> "current" binaries.
>
> The
Hello,
We plan to use a SVN repository as a deployment mechanism so technicians
can download and install the application binaries for a customer system.
The directory where we want them to download from will always have the
"current" binaries.
The issue I am facing is how to replace (overwrite)
On 04/19/2013 12:47 PM, C. Michael Pilato wrote:
>>> I found that this can be done with the svn command line tools. However,
>>> --force must be used. Without --force, svn will see that the file has
>>> svn:mime-type prop set to application/octet-stream and refuse to do
>>> anything to a binary fil
On Fri, May 3, 2013 at 8:57 AM, Marek Slama wrote:
> So it seems I will have to set eol-style explicitly on all my text files. I
> will have to investigate how to set eol-style
> for newly added file for different clients my teammates use on Win. On Linux
> I can set it in config file using auto-p
On 05/03/2013 09:57 AM, Marek Slama wrote:
> So it seems I will have to set eol-style explicitly on all my text files. I
> will have to investigate how to set eol-style
> for newly added file for different clients my teammates use on Win. On Linux
> I can set it in config file using auto-props.
Su
So it seems I will have to set eol-style explicitly on all my text files. I
will have to investigate how to set eol-style
for newly added file for different clients my teammates use on Win. On Linux
I can set it in config file using auto-props.
Thanks for info
Marek
-- Původní zpráva
On 05/03/2013 09:21 AM, Marek Slama wrote:
> Hi,
>
> not sure why but my svn client does not convert line endings for 'some'
> of my files. I did not find any rule for this. I have java project and
> files are text java sources. There is no mime type or eol-style property
> set on given files and
Hi,
not sure why but my svn client does not convert line endings for 'some' of
my files. I did not find any rule for this.
I have java project and files are text java sources. There is no mime type
or eol-style property set on given files and
some are with Linux line endings and some with DOS li
On Thu, May 2, 2013 at 7:35 PM, Os Tyler wrote:
> Thanks in advance for any help here.
>
> We're using svnserve and I've successfully implemented SASL authentication
> against our company Active Directory LDAP instance. And our windows and
> linux clients are successfully connecting.
>
> However t
17 matches
Mail list logo
