On Fri, Apr 26, 2013 at 08:06:50AM -, br...@apache.org wrote:
Author: brane
Date: Fri Apr 26 08:06:50 2013
New Revision: 1476092
URL: http://svn.apache.org/r1476092
Log:
* CHANGES: Added note about case-sensitive user and group names in authz
config.
Should we add a corresponding
On 26.04.2013 11:16, Stefan Sperling wrote:
On Fri, Apr 26, 2013 at 08:06:50AM -, br...@apache.org wrote:
Author: brane
Date: Fri Apr 26 08:06:50 2013
New Revision: 1476092
URL: http://svn.apache.org/r1476092
Log:
* CHANGES: Added note about case-sensitive user and group names in authz
Bert Huijben b...@qqmail.nl writes:
However the fact that the missing empty cache is created and populated
is just a fortuitous side effect of how we handle externals[1].
There is nothing special about externals in the following code.
I've added a regression test for inherited properties to
/subversion/trunk/subversion/libsvn_wc/wc-metadata.sql
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
We should probably also test this on an upgrade from entries as in that
case we don't get through the upgrade query.
Bert From: Philip
Bert Huijben b...@qqmail.nl writes:
/subversion/trunk/subversion/libsvn_wc/wc-metadata.sql
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
We should probably also test this on an upgrade from entries as in that
case we don't get
Mark Phippard markp...@gmail.com writes:
That said, I did misunderstand the proposal. I thought it was
suggesting we should just make things case-INsensitive. I thought
that would be the wrong decision at this point.
The file has always been case sensitive. So if you are just fixing a
Philip Martin wrote on Fri, Apr 26, 2013 at 15:07:01 +0100:
defines a single group (= mp) and single access rule (= rw). Now that
is still a contrived example but something like this is more likely:
[groups]
Read_Users = philip
[/]
@Read_users = r
The new
Daniel Shahaf danie...@elego.de writes:
Philip Martin wrote on Fri, Apr 26, 2013 at 15:07:01 +0100:
defines a single group (= mp) and single access rule (= rw). Now that
is still a contrived example but something like this is more likely:
[groups]
Read_Users = philip
[/]
I'm not sure how many vim users there are around here besides me, as I
recall there was an awful lot of Emacs users out there. However, I
got tired of seeing my compiler warnings caught by other people after
I'd committed.
So two fairly useful plugins for vim are:
Syntastic (syntax checking):
URL: http://svn.apache.org/r1476374
Log:
Add support for YouCompleteMe vim plugin.
Needs the following tools to be useful:
YouCompleteMe: https://github.com/Valloric/YouCompleteMe
Bear: https://github.com/rizsotto/Bear
* .ycm_extra_conf.py: Add config file for YouCompleteMe plugin,
(Forwarding to dev@, on the assumption that's what C-Mike intended.)
C. Michael Pilato wrote:
On 04/25/2013 07:32 PM, Julian Foad wrote:
While reviewing r1475724 Fix changelist filtering when --changelist
values aren't UTF8, I noticed we also fail to convert some other
command-line options to
On Fri, Apr 26, 2013 at 2:29 PM, Julian Foad julianf...@btopenworld.com wrote:
Hi Ben. I believe you need to add a copyright/whatever boiler-plate header
to this new file. If it also included a comment saying what it is for and
where it came from, that would be awesome.
Also a comment in
On Fri, Apr 26, 2013 at 1:09 PM, Ben Reser b...@reser.org wrote:
The mainline of Bear doesn't have working OS X support (yet), but you
can find it ported for OS X here (you'll need to use the
porting_to_osx branch):
https://github.com/breser/Bear/tree/porting_to_osx
The OS X port work has
[Ben Reser]
I've added the needed .ycm_extra_conf.py and a make target to produce
the compilation database in r1476374. So using these plugins with the
Subversion code base should be as simple as installing the plugins
into vim per their directions, installing bear, running make clean
make
On Fri, Apr 26, 2013 at 5:57 PM, Peter Samuelson pe...@p12n.org wrote:
Speaking of 'make clean', compile_commands.json really needs to be in
either CLEAN_FILES or EXTRACLEAN_FILES.
Probably, extra clean because I don't think I'd want this removed most
of the time.
Also, it sounds like
On Fri, Apr 26, 2013 at 6:18 PM, Ben Reser b...@reser.org wrote:
On Fri, Apr 26, 2013 at 5:57 PM, Peter Samuelson pe...@p12n.org wrote:
Speaking of 'make clean', compile_commands.json really needs to be in
either CLEAN_FILES or EXTRACLEAN_FILES.
Probably, extra clean because I don't think I'd
16 matches
Mail list logo
