Bert Huijben b...@qqmail.nl writes:
*
But I would also like to recommend/ask that we start bundling Sqlite with
Subversion, to allow optimizing for the specific version we use for a
release without risking future breakage.
*
Are we able to get advance notice of SQLite security
Fredrik Orderud wrote:
Over the past year, there have been several discussions regarding undesirable
side-effects of the currently (too) permissive merge mode on this list. As
of today, subversion will silently discard changes (instead of signaling a
conflict) under certain merging
Daniel Shahaf wrote:
Andreas Stieger wrote on Sat, Nov 16, 2013 at 00:08:40 +:
subversion/tests/libsvn_fs_base/fs-base-test.c:239:6: warning: 'present'
may be used uninitialized in this function [-Wmaybe-uninitialized] et
al. Initializing to boolean value that would fail the test if
Summary:
+1 to release
Platform:
Linux (Debian/wheezy)
Tested:
(local, svn, svn+sasl, serf, neon) x (fsfs, fsfs/pack/shard, bdb)
(serf/v1, neon/v1) x (fsfs, bdb)
swig-pl, swig-py, swig-rb, ctypes-python
javahl x (fsfs, bdb)
Results:
All tests PASS except for known failure of
Summary:
+1 to release
Platform:
Linux (Debian/wheezy) 64-bit
Tested:
(local, svn, svn/sasl, serf, serf/v1) x (fsfs, fsfs/pack/shard, bdb)
swig-pl, swig-py, swig-rb, ctypes-python
javahl x (fsfs, bdb)
Results:
All tests successful except for expected failures of
Hi,
Running
$ svn diff folder --depth=empty
still produces the diff for all added children as well, even though the
depth was set to empty.
$ mkdir folder
$ echo test folder/file
$ svn add folder
$ svn diff folder --depth=empty patch.diff
now the file patch.diff also contains the diff for
On 18.11.2013 20:05, Stefan Kueng wrote:
Hi,
Running
$ svn diff folder --depth=empty
still produces the diff for all added children as well, even though
the depth was set to empty.
$ mkdir folder
$ echo test folder/file
$ svn add folder
$ svn diff folder --depth=empty patch.diff
I (Julian Foad) wrote:
Fredrik Orderud wrote:
Could if be possible to add strict conflicts to the most wanted
list on the Subversion roadmap webpage?
If nobody objects, I'll add that to the list later today. [...]
Done.
- Julian
[1]
On Mon, Nov 18, 2013 at 9:39 PM, Julian Foad julianf...@btopenworld.comwrote:
I (Julian Foad) wrote:
Fredrik Orderud wrote:
Could if be possible to add strict conflicts to the most wanted
list on the Subversion roadmap webpage?
If nobody objects, I'll add that to the list later today.
Following r1543145, the attached patch adds __attribute__((sentinel)) to
functions that require a null sentinel argument, to make GCC warn if the
argument is missing. Via a macro so only for GCC = 4.0. (I don't see an
equivalent attribute for MSC but if there is one we can add it.)
The patch also
On 11/18/13 3:03 PM, Julian Foad wrote:
If no objections I'll commit tomorrow.
On further thinking I don't think SWIG should be excluded in this case. It
makes sense to exclude it from the SVN_DEPRECATED warnings with SWIG because we
expect the SWIG bindings to implement deprecated functions
11 matches
Mail list logo
