Hi All
We read folks posted online and it appears to show conflicting statements
on how to svn ignore multiple directories and files using svn propedit.
Suppose we have the following working copy directory structure.
/projectRoot (this working copy directory contains subdirectories build and
src
Hi All
Q: During SVN merge, does it read svn ignore list to ignore files,
directories to not merge them to a working copy directory from a repository
?
Thank you.
Sincerely
Hello,
On 04/08/13 09:55, Z W wrote:
> Q: During SVN merge, does it read svn ignore list to ignore files,
> directories to not merge them to a working copy directory from a
> repository ?
The svn:ignore properties is for ignoring *unversioned* files usually
generated during a build. It does not w
Hello,
On 04/08/13 09:52, Z W wrote:
> classes/*.class
> README.txt
> build/artifacts/jars/*.jars
> build/artifacts/zips/*.zips
svn:ignore patterns are not recursive. You have to set svn:ignore on
each dir separately. See [1]
So...
* set svn:ignore property on "classes" with "*.class"
* set svn:
Guten Tag Felipe Alvarez,
am Sonntag, 4. August 2013 um 06:41 schrieben Sie:
> 'm using tortoiseSVN, and noticed that when updating the very root
> of the repository, locks which I have taken under it become broken. Here is
> output from cygwin.
Maybe I'm missing something but what exactly is b
On 4 Aug 2013 05:44, "Z W" wrote:
>
> Hi All
>
> We have a branch A
> We svn copy A to feature branch Y
> Time elapsed
> We svn merge A to Y continuously
> Time elapsed
> We svn copy A to branch B (and decided B would be the "trunk")
> Time elapsed
> We have been merging B to Y continuously
> We h
According to the release notes:
http://subversion.apache.org/docs/release-notes/1.8.html#fsfs-enhancements
We should have seen a bump in the FSFS format number to '6' for 1.8.
But when I'm looking at the 'format' file inside the FSFS repository
directory on the server, I'm seeing '5'.
# svnad
On Aug 4, 2013, at 15:44, Thomas Harold wrote:
> According to the release notes:
> http://subversion.apache.org/docs/release-notes/1.8.html#fsfs-enhancements
>
> We should have seen a bump in the FSFS format number to '6' for 1.8. But when
> I'm looking at the 'format' file inside the FSFS repo
Maybe I'm missing something but what exactly is broken in your
> output? It ends with svn up, but shouldn't be there at least one
> additional svn st to show something about the lock?
>
> > Felipe@FELIPES ~/SVN
> > $ svn up
> > Updating '.':
> > BTrunk\SystemAdmin\rsync_transfer.cron.FreshASPN
On 8/4/2013 6:30 PM, Ryan Schmidt wrote:
Check the file /backup/svndump/test3/db/format.
# cat /backup/svndump/test3/db/format
6
layout sharded 1000
Okay, so I was looking at the wrong thing.
That still raises the question (in my mind) of why the two values are
different on a freshly create
Please use reply all to keep things on the list. Also please don't
top-post, i.e. respond inline or at the bottom. More below ...
On 4 Aug 2013 22:45, "Z W" wrote:
>
> Hi Johan
>
> Thanks for responding.
> We are using 1.6 client.
> 1- Will reintegrate work ?
I think so, but YMMV, and you won't
I'm exploring subversion 1.8.1 API, and wondering whether there is any
example for svn_client_update().
The examples in source code are of little help.
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list
13 matches
Mail list logo
