Julian Foad wrote:
> Stefan Kueng wrote:
>> Another reason to store whole files: patches don't work with non-text
>> files. Which is a major problem especially on Windows where files often
>> are encoded in utf16.
>
> Making 'svn diff' and 'svn patch' support non-text files is already a
>
Stefan Kueng wrote:
> Another reason to store whole files: patches don't work with non-text
> files. Which is a major problem especially on Windows where files often
> are encoded in utf16.
Making 'svn diff' and 'svn patch' support non-text files is already a
dependency of
On 01.09.2017 17:24, Julian Foad wrote:
Stefan Sperling wrote:
On Fri, Sep 01, 2017 at 03:01:33PM +0100, Julian Foad wrote:
The above behaviour looks good to me.
However, as you already pointed out, matching child path components
seems to be impossible at present:
$ svn ls -r3 --pattern
On 02.09.2017 18:06, Stefan Fuhrmann wrote:
>
>
> On 02.09.2017 17:17, Branko Čibej wrote:
>> On 02.09.2017 17:12, stef...@apache.org wrote:
>>> +svn_boolean_t
>>> +svn_utf__fuzzy_glob_match(const char *str,
>>> + const apr_array_header_t *patterns,
>>> +
On 01.09.2017 15:31, Branko Čibej wrote:
On 01.09.2017 06:36, Stefan Fuhrmann wrote:
On 29.08.2017 14:04, Branko Čibej wrote:
On 29.08.2017 13:28, Stefan Sperling wrote:
On Tue, Aug 29, 2017 at 01:12:07PM +0200, Stefan Fuhrmann wrote:
How would you implement the case-insensitive
On 02.09.2017 17:17, Branko Čibej wrote:
On 02.09.2017 17:12, stef...@apache.org wrote:
+svn_boolean_t
+svn_utf__fuzzy_glob_match(const char *str,
+ const apr_array_header_t *patterns,
+ svn_membuf_t *buf)
+{
+ const char *normalized;
+
On 02.09.2017 17:12, stef...@apache.org wrote:
> +svn_boolean_t
> +svn_utf__fuzzy_glob_match(const char *str,
> + const apr_array_header_t *patterns,
> + svn_membuf_t *buf)
> +{
> + const char *normalized;
> + svn_error_t *err;
> + int i;
> +
>
The OSX build slave is failing on a couple of the conflict resolver
tests over ra_svn. Can someone please take the time to figure it out?
Otherwise my maintaining the build slave makes no sense ...
-- Brane
On Sat, Sep 02, 2017 at 08:18:00AM +, Daniel Shahaf wrote:
> [replying to multiple]
>
> James McCoy wrote on Fri, Sep 01, 2017 at 08:15:05 -0400:
> > On Fri, Sep 01, 2017 at 03:07:16AM +, Daniel Shahaf wrote:
> > > I'm not sure I'm getting through here.
> > >
> > > The note does say
Daniel Shahaf wrote on Sat, Sep 02, 2017 at 08:18:00 +:
> However, I find the docstring ambiguous and you do not.
.oO ( Doesn't this _ipso facto_ mean the docstring is ambiguous? )
Bob Zhu wrote on Fri, Sep 01, 2017 at 10:13:39 -0700:
> We definitely don't wan to do anything client side since that would be a
> nightmare to manage afterwards.
> Upper management essentially wants this reminder everytime they do a
> checkout. Almost like a disclaimer that they have to agree to
[replying to multiple]
James McCoy wrote on Fri, Sep 01, 2017 at 08:15:05 -0400:
> On Fri, Sep 01, 2017 at 03:07:16AM +, Daniel Shahaf wrote:
> > I'm not sure I'm getting through here.
> >
> > The note does say "Don't allocate one of these yourself" but in the
> > second sentence implies
On 27.08.2017 02:09, Branko Čibej wrote:
On 27.08.2017 02:04, Daniel Shahaf wrote:
Julian Foad wrote on Fri, 25 Aug 2017 21:42 +0100:
Let's clarify. We can mean two possible things when we say 'a series of
patches':
1. "patch versions": a series of successively better patches, all
13 matches
Mail list logo
