The cygwin version of Subversion is a unix compilation of subversion running on
Windows, via the cygwin libraries. As such it doesn't understand special
Windoes paths.
If you would use a normal windows client (compiled for windows; not cygwin) it
would understand that it should transform file:
Hi,
I've been using subversion on my Windows 7 PC with Cygwin with a repository on
a Linux server accessed via file://.
I installed a brand new Cygwin version yesterday.
My local workspace lost its connection to the repository.
I can no longer access via svn the repository which I was previously
Hi,
If you're using Subversion 1.8, you may find this thread relevant:
http://thread.gmane.org/gmane.comp.version-control.subversion.user/118260
It describes specific instances in which Subversion 1.8 (and later)
add mergeinfo to nodes. The mergeinfo there may be safely removed.
--Pete
On Thu
Thanks guys, that worked.
Hi Chris,
Hi,
we've been using SVN for a large in-house project for a number of years and the longer
time goes by, the more strange the svn:mergeinfo properties behave. I don't know if the
"issues" are completely expected, if our repository somehow has ended up in a
state that is unwanted or
Hi,
we've been using SVN for a large in-house project for a number of years and the
longer time goes by, the more strange the svn:mergeinfo properties behave. I
don't know if the "issues" are completely expected, if our repository somehow
has ended up in a state that is unwanted or if there's s
Thanks a lot. I am a newbie to shell script. I appreciate your help.
On 25 Jun 2015 13:45, "Branko Čibej" wrote:
> On 25.06.2015 10:10, Dhiraj Prajapati wrote:
>
> Below is the code snippet I am using. I need the file contents in a
> variable.
>
>
> *fileContents=`$SVNLOOK cat $REPOS $FNAME -t
On 25.06.2015 10:15, Scott Aron Bloom wrote:
>
> If the variable $TXN contains a *, it is getting expanded by the echo
> command, unix is expanding that before the echo is called.
>
>
>
> I would put single around the variable on your echo command
>
A single quote would make the command print:
If the variable $TXN contains a *, it is getting expanded by the echo command,
unix is expanding that before the echo is called.
I would put single around the variable on your echo command
From: Dhiraj Prajapati [mailto:dhiraj.prajap...@games24x7.com]
Sent: Thursday, June 25, 2015 1:10 AM
To: Br
On 25.06.2015 10:10, Dhiraj Prajapati wrote:
> Below is the code snippet I am using. I need the file contents in a
> variable.
>
> *fileContents=`$SVNLOOK cat $REPOS $FNAME -t $TXN`
> *
> *echo "contents:" $fileContents 1>&2*
>
> Am I doing anything wrong?
Yes of course you are. You really should
Below is the code snippet I am using. I need the file contents in a
variable.
*fileContents=`$SVNLOOK cat $REPOS $FNAME -t $TXN`*
*echo "contents:" $fileContents 1>&2*
Am I doing anything wrong?
-Dhiraj
On Thu, Jun 25, 2015 at 1:37 PM, Branko Čibej wrote:
> On 25.06.2015 09:31, Dhiraj Praja
On 25.06.2015 09:31, Dhiraj Prajapati wrote:
> Hi,
> I have a pre-commit hook which validates the contents of the files
> being committed before commit.
> I am using /svnlook cat/ command to read the contents of the file
> being committed.
> However, whenever there is a leading slash on a particula
Hi,
I have a pre-commit hook which validates the contents of the files being
committed before commit.
I am using *svnlook cat* command to read the contents of the file being
committed.
However, whenever there is a leading slash on a particular line in the
file, the *svnlook cat* command fails to di
13 matches
Mail list logo
