dear,
our program call the api "svn_auth_ssl_server_trust_prompt_func_t" in
windows can ignore server invaild certificate,
code like :
svn_client_get_ssl_server_trust_prompt_provider(
&provider, onSslServerTrustPrompt, this, pool);
*(svn_auth_pro
Stefan Sperling wrote:
> http://svn.apache.org/r1668625
>
> I will nominate this for backport to 1.9 shortly. Note that there is
> no guarantee it will show up in 1.9.0 until the release happened.
Please nominate for 1.8 as well. It can well be justified as a bug fix.
- Julian
On Mon, Mar 23, 2015 at 12:11:37PM +0100, Stefan Sperling wrote:
> On Mon, Mar 23, 2015 at 02:43:20AM -0700, Chris wrote:
> > Please consider either adding this "filtering", or an error message in
> > future releases.
>
> Working on it...
http://svn.apache.org/r1668625
I will nominate this for
On Mon, 3/23/15, Julian Foad wrote:
Subject: Re: diff --summarize --ignore-properties
To: "Chris"
Cc: "dev"
Date: Monday, March 23, 2015, 12:26 PM
Hi Chris.
On 23 March 2015 at 09:43,
Chris wrote:
> searching fo
Hi Chris.
On 23 March 2015 at 09:43, Chris wrote:
> searching for previous information on a problem I'm checking up on, I found
> the below discusion on this list:
>
> http://subversion.1072662.n5.nabble.com/svn-diff-summarize-with-ignore-properties-or-properties-only-td192046.h
On Mon, Mar 23, 2015 at 02:43:20AM -0700, Chris wrote:
> Please consider either adding this "filtering", or an error message in future
> releases.
Working on it...
Hi,
searching for previous information on a problem I'm checking up on, I found the
below discusion on this list:
http://subversion.1072662.n5.nabble.com/svn-diff-summarize-with-ignore-properties-or-properties-only-td192046.html
I apologize if this is the wrong list for posting this query
s/libsvn_fs_fs/fs-fs-fuzzy-test.c
A subversion/tests/libsvn_fs_fs/fs-fs-private-test.c
M subversion/tests/libsvn_fs_fs/fs-fs-pack-test.c
M subversion/tests/libsvn_fs_fs
$ svn diff --summarize -r163:164 subversion/tests/libsvn_fs_fs
--ignore-properties
MM subversion/test
subversion/tests/libsvn_fs_fs
$ svn diff --summarize -r163:164 subversion/tests/libsvn_fs_fs
--ignore-properties
MM subversion/tests/libsvn_fs_fs/fs-fs-fuzzy-test.c
A subversion/tests/libsvn_fs_fs/fs-fs-private-test.c
M subversion/tests/libsvn_fs_fs/fs-fs-pack
-test.c
M subversion/tests/libsvn_fs_fs
$ svn diff --summarize -r163:164 subversion/tests/libsvn_fs_fs
--ignore-properties
MM subversion/tests/libsvn_fs_fs/fs-fs-fuzzy-test.c
A subversion/tests/libsvn_fs_fs/fs-fs-private-test.c
M subversion/tests/libsvn_fs_fs/fs-fs
On 02/05/2014 05:45 AM, Julian Foad wrote:
> C. Michael Pilato wrote:
>
>> Mostly looking
>> for general feedback on the idea of the "sounds useful if it works" or
>> "you *really* don't want to go there" variety, but deeper review is of
>> course welcome, too.
>
> It seems a reasonable enhanceme
Daniel Shahaf wrote:
> C. Michael Pilato wrote:
>> Introduce '--ignore-dates' option for 'svnadmin load',
>
> [...] However, 'load --ignore-dates' has another use-case: preventing
> the "-r {DATE} doesn't work as intended" syndrome
Fuhrmann [mailto:stefan.fuhrm...@wandisco.com]
Sent: woensdag 5 februari 2014 06:08
To: Branko Čibej
Cc: Subversion Development
Subject: Re: [PATCH][RFC] svnadmin load --ignore-dates
On Wed, Feb 5, 2014 at 6:03 AM, Stefan Fuhrmann mailto:stefan.fuhrm...@wandisco.com> > wrote:
On Wed, Feb 5, 201
C. Michael Pilato wrote:
> Mostly looking
> for general feedback on the idea of the "sounds useful if it works" or
> "you *really* don't want to go there" variety, but deeper review is of
> course welcome, too.
It seems a reasonable enhancement to me. Simple and to the point.
(A couple of style
On Wed, Feb 5, 2014 at 6:03 AM, Stefan Fuhrmann <
stefan.fuhrm...@wandisco.com> wrote:
> On Wed, Feb 5, 2014 at 4:02 AM, Branko Čibej wrote:
>
>> On 05.02.2014 03:10, Daniel Shahaf wrote:
>>
>> However, 'load --ignore-dates' has another use-case: prev
On Wed, Feb 5, 2014 at 4:02 AM, Branko Čibej wrote:
> On 05.02.2014 03:10, Daniel Shahaf wrote:
>
> However, 'load --ignore-dates' has another use-case: preventing the "-r
> {DATE} doesn't work as intended" syndrome when loading a project's history
&g
On 05.02.2014 03:10, Daniel Shahaf wrote:
> However, 'load --ignore-dates' has another use-case: preventing the
> "-r {DATE} doesn't work as intended" syndrome when loading a project's
> history into an existing repository.
I would argue that this is an i
or
> "you *really* don't want to go there" variety, but deeper review is of
> course welcome, too.
>
> Log message:
>
> {{{
> Introduce '--ignore-dates' option for 'svnadmin load', which causes
> the load process to ignore the revision da
view is of
course welcome, too.
Log message:
{{{
Introduce '--ignore-dates' option for 'svnadmin load', which causes
the load process to ignore the revision datestamps found in the
dumpstream. This allows folks to more easily use dumpfiles as
repository templates whi
On 12/4/13 3:09 PM, Evgeny Kotkov wrote:
> I've attached a patch to fix this issue. AFAIK [1], SVNKit does not include
> the "j" version of svnrdump, so I did not touch the part of the setup that
> handles the --use-jsvn option. Log message:
> [[[
> Do not ignor
AFAIK [1], SVNKit does not include
the "j" version of svnrdump, so I did not touch the part of the setup that
handles the --use-jsvn option. Log message:
[[[
Do not ignore --bin parameter for svnrdump when running Python tests.
* subversion/tests/cmdline/svntest/main.py
(svnrdump_bina
Stefan Fuhrmann wrote:
> On Thu, Nov 21, 2013 at 8:18 PM, Julian Foad wrote:
>> In r1544253 I added error checking to some socket initiliazation cases.
>> I haven't reproduced such errors, I just followed the obvious coding
>> pattern to add the missing checks.
>>
>> I would appreciate a review o
On Thu, Nov 21, 2013 at 8:18 PM, Julian Foad wrote:
> Bert mentioned to me that svnserve sometimes exits successfully after a
> genuine fatal error.
>
> In r1544253 I added error checking to some socket initiliazation cases. I
> haven't reproduced such errors, I just followed the obvious coding pa
Bert mentioned to me that svnserve sometimes exits successfully after a
genuine fatal error.
In r1544253 I added error checking to some socket initiliazation cases. I
haven't reproduced such errors, I just followed the obvious coding pattern
to add the missing checks.
I would appreciate a review
cases Subversion doesn't handle very well.
We need to address the source of the problem. Hiding the problem
with an --ignore-properties option is not a solution.
Please explain in detail the merges which result in the creation
of the mergeinfo you don't want. Perhaps there is a bug t
Hi,
On Thu, Nov 7, 2013 at 3:16 PM, Stefan Sperling wrote:
> Is there a way to exclude mergeinfo changes from commit? I.e. to use
> > --ignore-properties for svn merge in the same way as for svn diff?
> >
> > Rationale: imagine a feature branch which is created for implem
On Thu, Nov 07, 2013 at 09:43:24AM +0100, Sergei Riaguzov wrote:
> Hi,
>
> Is there a way to exclude mergeinfo changes from commit? I.e. to use
> --ignore-properties for svn merge in the same way as for svn diff?
>
> Rationale: imagine a feature branch which is created for
Hi,
Is there a way to exclude mergeinfo changes from commit? I.e. to use
--ignore-properties for svn merge in the same way as for svn diff?
Rationale: imagine a feature branch which is created for implementing just
one feature. There are many commits with messages like "grrr..." o
On Fri, Sep 27, 2013 at 12:40 AM, Ben Reser wrote:
> On 9/26/13 12:45 PM, Mark Moe wrote:
>> We found that about half the performance issue was solved by using
>> "SVNPathAuthz off" while the other half was solved by skipping that
>> big revision when doing svn log -v. Just the sheer transfer of
.
Also beware that if you replace a repository you need to restart the server in
order to invalidate caches since at current the server believes that the
content it has already cached is the same as long as the UUID doesn't change.
> Although not as critical to us now, we still think svn log
On 9/26/13 2:34 AM, Stefan Sperling wrote:
> This sounds as if the performance issue was on the server side.
I ended up helping answer some of the questions behind this particular issue
and you are entirely correct.
> The client requests a list of changed paths if 'svn log' is run
> with the --ve
> > This has caused significant performance issues especially with svn log.
> > There reasoning was if they could ignore properties this would help combat
> > these performance issues.
> >
> > Does this make sense?
> This sounds as if the performance issue was o
formance issues especially with svn log.
> There reasoning was if they could ignore properties this would help combat
> these performance issues.
>
> Does this make sense?
This sounds as if the performance issue was on the server side.
The client requests a list of changed paths i
I believe this improvement request stems from the fact that Medtronic (the
customer) did a massive commit (to a very large change-set) setting the
properties of ~300k files.
This has caused significant performance issues especially with svn log.
There reasoning was if they could ignore properties
?
- Julian
> On Wed, Sep 4, 2013 at 1:53 PM, Patrick Sawyer wrote:
>> [...] do we have any discussion on this point? Would the ability to
>> ignore properties be useful?
>>
>> On Wed, Aug 21, 2013 at 6:40 PM, Patrick Sawyer wrote:
>> It may be useful to provide th
cannot think of any other scenario where this requests makes sense.
When I added the --diff option to 'svn log', I deliberately hard-coded
many of the available diff options to avoid growing 'svn log --diff' into
a full-blown complex replacement for 'svn diff'. I
. patrick.saw...@wandisco.com
On Wed, Sep 4, 2013 at 1:53 PM, Patrick Sawyer
wrote:
> I know the issue has been raised to to provide log to filter out
> change-sets:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4419
>
> But do we have any discussion on this point? Would the
I know the issue has been raised to to provide log to filter out
change-sets:
http://subversion.tigris.org/issues/show_bug.cgi?id=4419
But do we have any discussion on this point? Would the ability to ignore
properties be useful? Thanks
Regards
Patrick Sawyer | *Deployment Coordinator
It may be useful to provide the option to ignore properties when performing
an svn log.
This has been referred to in a previous post:
http://subversion.tigris.org/issues/show_bug.cgi?id=3690
Regards
Patrick Sawyer | *Deployment Coordinator *
*
*
WANdisco // *Non-Stop Data*
t. +44 (0)114
On Wed, May 15, 2013 at 1:52 PM, Stefan Sperling wrote:
> On Wed, May 15, 2013 at 11:38:17AM -, stef...@apache.org wrote:
> > Author: stefan2
> > Date: Wed May 15 11:38:17 2013
> > New Revision: 1482772
> >
> > URL: http://svn.apache.org/r1482772
> > Log:
> > CHANGES: update after reviewing
On Wed, May 15, 2013 at 11:38:17AM -, stef...@apache.org wrote:
> Author: stefan2
> Date: Wed May 15 11:38:17 2013
> New Revision: 1482772
>
> URL: http://svn.apache.org/r1482772
> Log:
> CHANGES: update after reviewing the r1293011 500 revs block
>
> Modified:
> subversion/trunk/CHANGES
rking copy.
Use of this option is not recommended!
Please run 'svn update' instead.
I believe --ignore-ancestry should be enough to disable
mixed-revisions check.
--ignore-ancestry (and --notice-ancestry) controls comparison beh
> Use of this option is not recommended!
> Please run 'svn update' instead.
>
> I believe --ignore-ancestry should be enough to disable
> mixed-revisions check.
--ignore-ancestry (and --notice-ancestry) controls com
e run 'svn update' instead.
I believe --ignore-ancestry should be enough to disable mixed-revisions
check.
Best wishes,
Andrey Paramonov
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Try '--allow-mixed-revisions'
--
Johan
On Tue, Jul 3, 2012 at 9:36 AM, Andrey Paramonov wrote:
> If you merge "the old way", i.e. specifying --ignore-ancestry, Subversion
> sometimes requires you to update your WC:
>
> svn: E195020: Cannot merge into mixed-re
If you merge "the old way", i.e. specifying --ignore-ancestry,
Subversion sometimes requires you to update your WC:
svn: E195020: Cannot merge into mixed-revision working copy
[x:x]; try updating first
It wasn't the case for 1.6, and thus may be considered a regre
Hi all, just a quick message to make it easier for me to set up list
processing of incoming mails.
ot; treated
as new files or not.
Gavin.
On 20/09/2011, at 7:07 AM, rupert.thurner wrote:
> On Sep 19, 3:05 pm, Philip Martin wrote:
>> "rupert.thurner" writes:
>>> with svn-1.6
>>
>>> svn co
>>> --ignore-externalshttps://gar.svn.sourcefor
On Sep 19, 3:05 pm, Philip Martin wrote:
> "rupert.thurner" writes:
> > with svn-1.6
>
> > svn co
> > --ignore-externalshttps://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/subversion
> > cd subverison/trunk
> > ln -s gar ../whatever
> > s
"rupert.thurner" writes:
> with svn-1.6
>
> svn co --ignore-externals
> https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/subversion
> cd subverison/trunk
> ln -s gar ../whatever
> svn st
> X gar
>
> with svn -1.7 this looks like:
>
> s
with svn-1.6
svn co --ignore-externals
https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/subversion
cd subverison/trunk
ln -s gar ../whatever
svn st
X gar
with svn -1.7 this looks like:
svn st
? gar
platform: solaris, http://opencsw.org
rupert.
>> From issue tracker:
> >> ======
> >> Add an option to ignore files with only property changes and no content
> >> changes.
> >> e.g. svn log --ignore-properties
> >>
> >> Motivation: many users are not interested in revi
;props_only)
>>>> + || (! text_modified && rb->ignore_props_only))
>>>> + return SVN_NO_ERROR;
>>>> +}
>>>> +
>>>> + if (! rb->discover_changed_paths)
>>>> + log_entry->changed_paths2
Noorul Islam K M writes:
> Philip Martin writes:
>
>> Noorul Islam K M writes:
>>
>>> +static svn_error_t *
>>> +props_only_receiver(void *baton, svn_log_entry_t *log_entry, apr_pool_t
>>> *pool)
>>> +{
>>> + props_only_receiver_baton_t *rb = baton;
>>> +
>>> + if (log_entry->changed_paths2)
Philip Martin writes:
> Noorul Islam K M writes:
>
>> +static svn_error_t *
>> +props_only_receiver(void *baton, svn_log_entry_t *log_entry, apr_pool_t
>> *pool)
>> +{
>> + props_only_receiver_baton_t *rb = baton;
>> +
>> + if (log_entry->changed_paths2)
>> +{
>> + apr_array_header_t
Noorul Islam K M writes:
> +static svn_error_t *
> +props_only_receiver(void *baton, svn_log_entry_t *log_entry, apr_pool_t
> *pool)
> +{
> + props_only_receiver_baton_t *rb = baton;
> +
> + if (log_entry->changed_paths2)
> +{
> + apr_array_header_t *sorted_paths;
> + int i;
> +
Julian Foad writes:
> Noorul Islam K M wrote:
>
>> From issue tracker:
>> ==
>> Add an option to ignore files with only property changes and no content
>> changes.
>&
Noorul Islam K M wrote:
> From issue tracker:
> ==
> Add an option to ignore files with only property changes and no content
> changes.
> e.g. svn log --ignore-properties
>
> Motivation: many use
I thought of replying to the following thread, but unfortunately I lost
all my mails. So I am quoting the link.
http://svn.haxx.se/dev/archive-2011-07/0005.shtml
>From issue tracker:
==
Add an option to ignore fi
issue tracker. Pasting it
here.
Add an option to ignore files with only property changes and no content
changes. e.g. svn log --ignore-properties
Motivation: many users are not interested in reviewing changes to
property changes and only care about content changes.
I would like to give summary
On 06/29/2011 08:07 AM, Julian Foad wrote:
> My question is about this case:
>
> $ svn copy SOURCE TARGET@HEAD
>
> This case falls under the last sentence of point (C) above. Issue #3651
> [3] claims that the 'HEAD' peg should be ignored in this case, and that
> claim is explicitly tested by c
Julian Foad wrote on Wed, Jun 29, 2011 at 13:07:01 +0100:
> My question is about this case:
>
> $ svn copy SOURCE TARGET@HEAD
>
> This case falls under the last sentence of point (C) above. Issue #3651
> [3] claims that the 'HEAD' peg should be ignored in this case, and that
> claim is explici
o exist. Then, if someone else moves TARGET to another path
while we are composing and executing this command, Subversion could do
its best to follow the move or error out if it can't do so. But unless
and until 'svn' actually uses the peg revision in this way, it should
complain,
Problem was that the list address was getting rewritten to dev@a.o.
Fixed by tweaking postfix's configuration.
On Tue, May 10, 2011 at 10:56:52PM +, ne...@apache.org wrote:
> test mail from the vm
test mail from the vm
into its own child
> >> '/tmp/svn/wc1/trunk'
> >> % $svn cp ^/ ^/trunk -mm
> >
> > Hi Daniel,
> >
> > Should we even allow a copy of r0? What exactly does it mean and how
> > is it useful?
> >
>
mmit
>>> > svn switch /trunk .
>>> >
>>>
>>> This used to work fine. But now I'm getting the following error messages:
>>>
>>> subversion/svn/switch-cmd.c:184: (apr_err=195012)
>>> > svn: E195012: Path '.' d
ng the following error messages:
>>
>> subversion/svn/switch-cmd.c:184: (apr_err=195012)
>> > svn: E195012: Path '.' does not share common version control ancestry with
>> > the requested switch location. Use --ignore-ancestry to disable this
>> &g
th '.' does not share common version control ancestry with
> > the requested switch location. Use --ignore-ancestry to disable this check.
> > subversion/libsvn_client/switch.c:201: (apr_err=195012)
> > svn: E195012: 'file:///home/djcbecroft/dev/sandpit/repositor
between branches -- not just
> some generic point-the-working-copy-wherever-you'd-like mechanism. We now
> have the power to enforce that in ways that were impractical years ago, so
> recently (after another fat-fingered-then-interrupted 'svn switch' left me
> with a corrupt working copy) I added that enforcement, but, as you noted,
> with the ability to disable that safety mechanism via the --ignore-ancestry
> switch.
>
I guess I can understand the reason behind the change. It was just a tad
weird seeing it pop up for a case that has always worked.
Apologies for the noise.
Cheers,
Daniel B.
n's way to switch between branches -- not just
some generic point-the-working-copy-wherever-you'd-like mechanism. We now
have the power to enforce that in ways that were impractical years ago, so
recently (after another fat-fingered-then-interrupted 'svn switch' left me
w
following error messages:
> >
> > subversion/svn/switch-cmd.c:184: (apr_err=195012)
> >> svn: E195012: Path '.' does not share common version control ancestry
> with
> >> the requested switch location. Use --ignore-ancestry to disable this
> check.
>
ushd workingcopy
>> svn mkdir trunk
>> svn commit
>> svn switch /trunk .
>>
>
> This used to work fine. But now I'm getting the following error messages:
>
> subversion/svn/switch-cmd.c:184: (apr_err=195012)
>> svn: E195012: Path '.' does no
o work fine. But now I'm getting the following error messages:
subversion/svn/switch-cmd.c:184: (apr_err=195012)
> svn: E195012: Path '.' does not share common version control ancestry with
> the requested switch location. Use --ignore-ancestry to disable this check.
> sub
on: 1064905
>>
>> URL: http://svn.apache.org/viewvc?rev=1064905&view=rev
>> Log:
>> On the ignore-mergeinfo-log branch:
>> Send the list of ignored prop mods from client to server over the SVN RA
>> protocol.
>>
>> * subversion/libsvn_ra_svn/client.c
>> (r
What about libsvn_ra_svn/protocol ?
hwri...@apache.org wrote on Fri, Jan 28, 2011 at 21:59:14 -:
> Author: hwright
> Date: Fri Jan 28 21:59:14 2011
> New Revision: 1064905
>
> URL: http://svn.apache.org/viewvc?rev=1064905&view=rev
> Log:
> On the ignore-mergeinfo-lo
Doug Culnane wrote on Thu, Jan 27, 2011 at 13:26:55 +0100:
> So the technical spec is if the command is ignore append the file or
> folder to its containing parent folders svn:ignore list.
% head .zshrc
svn() {
if [ "$1" = "ignore" ]; then
=svn propedit svn:ignore
Thanks for your response Stefan,
I am not a C programmer and do not have in dept knowledge of
subversion and it's client implementations but I have done a lot of
Java. So this is to be understood as a user feature request and not
much else.
I do not understand this:
svn ignore --depth=inf
On Thu, Jan 27, 2011 at 12:01:19PM +0100, Doug Culnane wrote:
> Guys,
>
> I understand how to use the svn:ignore but it is not the most
> convenient or logical user interface. Would it be possible to provide
> an ignore command line option that would provide a convenient
> inte
Guys,
I understand how to use the svn:ignore but it is not the most
convenient or logical user interface. Would it be possible to provide
an ignore command line option that would provide a convenient
interface to add files/folders to the ignore properties list?
ie:
dc@lt-dc:~/workspace/project
@a targets will also be returned.
> *
> - * If @a ignore_mergeinfo_changes is set, log will ignore any changes to
> - * the svn:mergeinfo property when determining which revisions to return.
> + * @a ignore_prop_mods is an optional hash of property names. If
> + * non-NULL, log w
On Wed, Aug 11, 2010 at 3:15 AM, Julian Foad wrote:
> On Tue, 2010-08-10, hwri...@apache.org wrote:
>> Author: hwright
>> Date: Tue Aug 10 20:59:29 2010
>> New Revision: 984208
>>
>> URL: http://svn.apache.org/viewvc?rev=984208&view=rev
>> Log:
>&
On Tue, 2010-08-10, hwri...@apache.org wrote:
> Author: hwright
> Date: Tue Aug 10 20:59:29 2010
> New Revision: 984208
>
> URL: http://svn.apache.org/viewvc?rev=984208&view=rev
> Log:
> On the ignore-mergeinfo branch:
> Fix a cast which was causing a segfault in sta
83 matches
Mail list logo
