On Tue, Mar 27, 2012 at 05:58:58PM +0200, Yves Martin wrote:
> Hello,
>
> I have used "svn log --diff path/to/myfile.txt"
> but the command generates history from the current working directory
> instead of limiting the report to the provided path.
>
> Is it the expected behavior ? If not please
On Tue, Mar 27, 2012 at 12:31 PM, Pietro Moras wrote:
> Dear Mark,
> -- PySvn as a Python API, clear enough.
> -- Now I'd expect that WorkBench would be a ready-to-use (Windows?)
> program. But, so far, I haven't been able to run it, nor to find any
> practical documentation clearly describing w
Dear Mark,
-- PySvn as a Python API, clear enough.
-- Now I'd expect that WorkBench would be a ready-to-use (Windows?) program.
But, so far, I haven't been able to run it, nor to find any practical
documentation clearly describing what it is.
What am I missing? Something very primordial,
Dear
Vishwajeet, Thanks
for your kind & quick answer.
>
better if you can tell what are you trying to do Well,
what I have got to do is simply to understand. Therefore, for
instance, you could describe me how you are possibly using PySvn
and/or WorkBench. I mean: not in detail, just in genera
> When I go to the download page for the Subversion binaries for WindowsOS:
>
> http://subversion.apache.org/packages.html
>
> Then there are 5 different packages:
>
> CollabNet (supported and certified by CollabNet; requires registration)
> SlikSVN
> (32- and 64-bit client MSI; maintained by B
Hello,
I have used "svn log --diff path/to/myfile.txt"
but the command generates history from the current working directory
instead of limiting the report to the provided path.
Is it the expected behavior ? If not please create an issue in tracker.
--
Yves Martin
On Tue, Mar 27, 2012 at 11:03 AM, Pietro Moras wrote:
> In need to understand what PySvn is all about (so to compare it with
> Slik-Subversion I'm currently using), downloaded and installed
> py27-pysvn-svn173-1.7.6-1457.exe and pysvn-workbench-svn173-1.6.6-1460.exe,
> I haven't got a clue what to
On Tue, Mar 27, 2012 at 8:33 PM, Pietro Moras wrote:
> In need to understand what PySvn is all about (so to compare it with
> Slik-Subversion I'm currently using), downloaded and installed
> py27-pysvn-svn173-1.7.6-1457.exe and pysvn-workbench-svn173-1.6.6-1460.exe,
> I haven't got a clue what t
In
need to understand what PySvn is all about (so to
compare it with Slik-Subversion I'm currently using), downloaded and
installed py27-pysvn-svn173-1.7.6-1457.exe and
pysvn-workbench-svn173-1.6.6-1460.exe, I haven't got a clue what to
do next.
Of
course I'm badly in need of some initial b
On Mon, Mar 26, 2012 at 5:43 AM, vishwajeet singh wrote:
> Hi All,
>
> I recently upgraded from subversion server from 1.6 to 1.7, everything
> works fine for 1.6 client and 1.7 server.
> But when I upgrade to 1.7 client my commit fails with following error
>
> *svn: E160013: Commit failed (detail
Philip Martin writes:
> vishwajeet singh writes:
>
>> As thread it's not just with mod_wsgi, problem persist with fcgi, can you
>> please elaborate on reordering I tried moving wsgi module at end but that
>> did not help.
>
> Reordering may not work; it depends how the other modules work. Fixin
On Mon, Mar 26, 2012 at 03:15:17PM -0500, John wrote:
> $ svn merge --record-only ^/myproject/trunk/subdir@2676 subdir
>
> $ svn pg 'svn:mergeinfo' subdir
> subdir - /myproject/branches/W/subdir:1488-2675
> /myproject/branches/Y/subdir:5925-7118
> /myproject/trunk/subdir:1488-7532
>
> $ svn pg 's
12 matches
Mail list logo
