Re: tortoise svn show log

[Ryan Schmidt]

On Feb 10, 2010, at 00:57, Ramachandran, Vishwanath(IE10) wrote:

> In the tortoise svn, show log does not show full log messages, by default I 
> guess it fetches 100 log messages, I need full log from 0’th revision to 
> up-date.
> How can I do that? I chose “show all” at the bottom, but still no luck
>  
> For .e.g. at the show log , on the date drop down menu, the date is today’s 
> date, I’ am not able to choose, earlier date, please suggest

You should ask this on the TortoiseSVN users mailing list instead. Many of us 
here do not use TortoiseSVN and cannot help you.

RE: tortoise svn show log

[Ramachandran, Vishwanath(IE10)]

Ok, what is the command ? if I need via command line
Svn log -v path , doesn't show full log

Regards
Vishwanath
Desk: +91 80 26588360 Extn: 48555



-Original Message-
From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com] 
Sent: Wednesday, February 10, 2010 1:51 PM
To: Ramachandran, Vishwanath(IE10)
Cc: users@subversion.apache.org
Subject: Re: tortoise svn show log

On Feb 10, 2010, at 00:57, Ramachandran, Vishwanath(IE10) wrote:

> In the tortoise svn, show log does not show full log messages, by
default I guess it fetches 100 log messages, I need full log from 0'th
revision to up-date.
> How can I do that? I chose "show all" at the bottom, but still no luck
>  
> For .e.g. at the show log , on the date drop down menu, the date is
today's date, I' am not able to choose, earlier date, please suggest

You should ask this on the TortoiseSVN users mailing list instead. Many
of us here do not use TortoiseSVN and cannot help you.

Re: tortoise svn show log

[Ryan Schmidt]

On Feb 10, 2010, at 02:33, Ramachandran, Vishwanath(IE10) wrote:

> Ok, what is the command ? if I need via command line
> Svn log -v path , doesn't show full log

"svn log" should show the full log. If your working copy is not up to date, it 
will only show the log up to the time of your working copy. Either "svn up" 
your working copy first or use "svn log " to work around that.

AW: Where to get SWIG SVN python binding binaries?

[Janosch Scharlipp]

Thanks Roman, i simply didn't see any reason to look inside the Apache 2.2
folder, since what i was doing didn't have to do anything with Apache.
My fault, but with the absolutely (:D) most recent version, it actually
works :)

Kind regards,
Janosch 


-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von ? 
Gesendet: Dienstag, 9. Februar 2010 21:27
An: users@subversion.apache.org
Betreff: Re: Where to get SWIG SVN python binding binaries?

Janosch Scharlipp  писал в своё
м письме Tue, 09 Feb 2010 23:13:59 +0300:

> Hi,
> Where can i get recent SWIG SVN python binding binaries? I tried the 
> most recent version from tigris.org (1.5.6 for py2.5) but it didn't 
> work together with my repositories (created with svn 1.6.6). (error 
> something like:
> "unsupported fs, expected 1..3 but found 4")

(Assuming you mean the Windows binaries)

How did you get the impression that it's the most recent version? You can
get the 1.6.6 bindings from the 1.6.6 release folder at
.

Roman.

new files on SVN

[Dominik Chmaj]

hello

I have problem with svn. I'm working with friend on project and sometimes only I
don't get new files submitted by someone. As I know I should be noticed about
all changes. I can see new files by issuing svn log or svn list, but svn up will
not fetch them. Svn st will not show any changes. So there is no file there on
my working copy, I can see it on SVN repo and there is nothing about change. Let
me know if this is know issue or maybe I'm doing something wrong.
Clean checkout will fetch everything - but this is taking quite much time. I
think here should be a way just to sync svn. Also let me know if this is not the
best place for this bug report.

ps. this is not client-related error, I got this on both windows and linux. We
upgraded svn to newest version and the problem is still there.

-- 
dmc

Problems during merge

[Christoph Bartoschek]

Hi, 

after a merge with conflicts I completely wrong conflict markers:


=== inv_merge.C =
...
   } else {
<<< .working
===
  _cur.sinks(to_polarity(other)).append(csol.sinks());
>>> .merge-right.r13821

  _cur.sinks(to_polarity(other)).append(csol.sinks());

  Time slew_limit =
...
==

In my working copy there is:

=== inv_merge.C.working ==
...
   } else {

  _cur.sinks(to_polarity(other)).append(csol.sinks());

  Time slew_limit =
...
==

The right part only differs in an empty line:

=== inv_merge.C.merge-right.r13821 ===
...
   } else {
  _cur.sinks(to_polarity(other)).append(csol.sinks());

  Time slew_limit =
...
==

In the left part we have: 

=== inv_merge.C.merge-left.r13820 ===
...
   } else {
  _cur.sinks(to_polarity(other)).append_slice(csol.sinks().begin(),
  csol.sinks().size());

  TimePair slew_limit =
...
==


I would have expected that I see the code of the left part in the merge view 
and not two times the code from working.

What is going wrong here?

Christoph

RE: new files on SVN

[Bert Huijben]

> -Original Message-
> From: Dominik Chmaj [mailto:d...@biuro.net.pl]
> Sent: woensdag 10 februari 2010 11:01
> To: users@subversion.apache.org
> Subject: new files on SVN
> 
> hello
> 
> I have problem with svn. I'm working with friend on project and
> sometimes only I
> don't get new files submitted by someone. As I know I should be noticed
> about
> all changes. I can see new files by issuing svn log or svn list, but
> svn up will
> not fetch them. Svn st will not show any changes. So there is no file
> there on
> my working copy, I can see it on SVN repo and there is nothing about
> change. Let
> me know if this is know issue or maybe I'm doing something wrong.
> Clean checkout will fetch everything - but this is taking quite much
> time. I
> think here should be a way just to sync svn. Also let me know if this
> is not the
> best place for this bug report.
> 
> ps. this is not client-related error, I got this on both windows and
> linux. We
> upgraded svn to newest version and the problem is still there.

Which Subversion release are you using?
(Subversion 1.6.0 and 1.6.1 had some issues on 'svn add' marking a directory 
sparse)

Are you using svn update --depth  for some of the updates?

In this case you could trigger issue #3569 
(http://subversion.tigris.org/issues/show_bug.cgi?id=3569)

As workaround for this specific issue I would recommend never using --depth (or 
-N) on svn update. (svn update --set-depth is safe)

Bert

Delete directory locally without causing svn diff to report changes

[David Cummings]

I'm looking for a way to remove a directory from my working copy
without it causing svn diff to report changes.

I often use svn co and svn up with --depth files to checkout partial
pieces of a repository.

For example I have the following repository structure:
trunk
  |--- folder1
  |--- folder2

To checkout trunk and folder 1 I would do:
svn checkout "file:///svn/project/tr...@head" -r HEAD
--ignore-externals --depth files
"/home/davey/ws/project_runtime/trunk3"
svn update "/home/davey/ws/project_runtime/trunk3/folder1" -r HEAD --depth files

This gives me a partial checkout of my repository. Most importantly
though, if I do an svn diff I do not see any changes.

Now sometimes I checkout everything, but then decide that I don't want
certain folders in my working copy. If I remove them using svn rm, and
then subsequently do an svn diff, I obviously see the deletion as a
change.

So I'm looking for a different command like svn rmlocal that would not
report this diff (essentially removing the deleted dir from the
.svn/entries). I can remove this data from the entries file, but it is
a pain. Is there an svn command that allows me to do this?

Thanks,
David

Re: Delete directory locally without causing svn diff to report changes

[Mark Phippard]

Don't you just want this?

http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html

Basically use the --depth feature to prune away what you do not want
rather than using svn rm.

Mark



On Wed, Feb 10, 2010 at 2:59 PM, David Cummings
 wrote:
> I'm looking for a way to remove a directory from my working copy
> without it causing svn diff to report changes.
>
> I often use svn co and svn up with --depth files to checkout partial
> pieces of a repository.
>
> For example I have the following repository structure:
> trunk
>  |--- folder1
>  |--- folder2
>
> To checkout trunk and folder 1 I would do:
> svn checkout "file:///svn/project/tr...@head" -r HEAD
> --ignore-externals --depth files
> "/home/davey/ws/project_runtime/trunk3"
> svn update "/home/davey/ws/project_runtime/trunk3/folder1" -r HEAD --depth 
> files
>
> This gives me a partial checkout of my repository. Most importantly
> though, if I do an svn diff I do not see any changes.
>
> Now sometimes I checkout everything, but then decide that I don't want
> certain folders in my working copy. If I remove them using svn rm, and
> then subsequently do an svn diff, I obviously see the deletion as a
> change.
>
> So I'm looking for a different command like svn rmlocal that would not
> report this diff (essentially removing the deleted dir from the
> .svn/entries). I can remove this data from the entries file, but it is
> a pain. Is there an svn command that allows me to do this?
>
> Thanks,
> David
>



-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: Delete directory locally without causing svn diff to report changes

[David Cummings]

Thank you Mark. Works like a charm :)

For those who don't want to follow the link, the following command was
what I was looking for:
svn update --set-depth=exclude 

On Wed, Feb 10, 2010 at 3:05 PM, Mark Phippard  wrote:
> Don't you just want this?
>
> http://blogs.open.collab.net/svn/2009/03/sparse-directories-now-with-exclusion.html
>
> Basically use the --depth feature to prune away what you do not want
> rather than using svn rm.
>
> Mark
>
>
>
> On Wed, Feb 10, 2010 at 2:59 PM, David Cummings
>  wrote:
>> I'm looking for a way to remove a directory from my working copy
>> without it causing svn diff to report changes.
>>
>> I often use svn co and svn up with --depth files to checkout partial
>> pieces of a repository.
>>
>> For example I have the following repository structure:
>> trunk
>>  |--- folder1
>>  |--- folder2
>>
>> To checkout trunk and folder 1 I would do:
>> svn checkout "file:///svn/project/tr...@head" -r HEAD
>> --ignore-externals --depth files
>> "/home/davey/ws/project_runtime/trunk3"
>> svn update "/home/davey/ws/project_runtime/trunk3/folder1" -r HEAD --depth 
>> files
>>
>> This gives me a partial checkout of my repository. Most importantly
>> though, if I do an svn diff I do not see any changes.
>>
>> Now sometimes I checkout everything, but then decide that I don't want
>> certain folders in my working copy. If I remove them using svn rm, and
>> then subsequently do an svn diff, I obviously see the deletion as a
>> change.
>>
>> So I'm looking for a different command like svn rmlocal that would not
>> report this diff (essentially removing the deleted dir from the
>> .svn/entries). I can remove this data from the entries file, but it is
>> a pain. Is there an svn command that allows me to do this?
>>
>> Thanks,
>> David
>>
>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>

SubVersion - Question

[Cristian Pascuzzi]

Hi

 

We are using Subversion on Linux server, with Windows clients. We have a
Configuration Administrator who makes the environments. We want a windows
toll that facilitate the administration of repositories for no expert user.
Is there any tool like that?

 

Regards

Cristian Pascuzzi

'.' is not a working copy error and resolution

[Todd Gleason]

One of our users came across a strange error trying to commit recently (with a 
1.6 client):

Action PathMime type
Command   Commit
Error   Commit failed (details follow):
Error   '.' is not a working copy
Finished!

On seeing this, you might think the directory he tried to commit had no .svn 
directory.  But it did.

After some investigation, it turned out that the parent directory (which was 
the C:\ root directory) had its own .svn directory.  He had accidentally done 
some sort of root-level checkout or move of a .svn directory to be under there. 
 I believe the result was that Subversion was seeing everything on that drive 
as not part of the working copy.  And indeed he couldn't commit from anything 
that he believed to be a Subversion working copy.

I understand that it was correct behavior for him to get a failure trying to 
commit, but I wanted to provide this information in case it's helpful to other 
users, and in case the developers want to change this sort of error to be more 
helpful, for example to indicate something about detecting a nested working 
copy, and including the two directories that conflict (the "real" WC root as 
well as the directory that is illegally nested).

Note that I don't think this use case will be obsolete even in 1.7 because I 
believe there will still be .svn directories directly under the WC root.

--Todd



Please consider the environment before printing this e-mail.

The contents of this e-mail message (including any attachments) are 
confidential to and are intended to be conveyed for the use of the recipient to 
whom it is addressed only. If you receive this transmission in error, please 
notify the sender of this immediately and delete the message from your system. 
Any distribution, reproduction or use of this message by someone other than 
recipient is not authorized and may be unlawful.

Fwd: Serving internal SVN path via Apache

[Itamar O]

Relocating the question to the correct mailing list + clarification:

I am not talking about serving multiple repositories with SVNParentPath.
I have a single repository with the following layout:
root (@ /var/svn/repos)
|- projA
|- projB
|- ...

Each project has its own virtual host on Apache,
with its own DNS's (e.g. www.projA.com & svn.projA.com).

I want that the svn.projA.com virtual host will be directed to root/projA,
so that users of projA SVN are not even aware of other projects.

Is this possible?

Thanks,
Itamar O.

-- Forwarded message --
From: Itamar O 
Date: Wed, Feb 10, 2010 at 11:00 PM
Subject: Serving internal SVN path via Apache
To: d...@subversion.apache.org


Is there a way to configure Apache to serve a "scoped" repository?
e.g., if my repository root is at /var/svn/repos,
and I have top-level project-structure,
I want something like:

  DAV svn
  SVNPath /var/svn/repos/projA
  # (this doesn't work..)
  # Maybe something like "SVNPath /var/svn/repos" & "SVNScope projA" ?


Thanks,
Itamar O.