On Sun, Dec 1, 2019 at 10:50 PM Daniel Shahaf wrote:
> Nathan Hartman wrote on Sun, Dec 01, 2019 at 22:22:26 -0500:
> > On a related note, I cannot seem to run *just* getopt_tests.py. If I
> > run it like this, I get failure:
(snip)
> > $ make check TESTS=subversion/tests/cmdline/getopt_tests.py
On Tue, Dec 3, 2019 at 10:41 PM Nathan Hartman
wrote:
> On Tue, Dec 3, 2019 at 5:15 PM Greg Stein wrote:
> > I was setting up a new chromebook, with a completely barren Ubuntu
> install (using ChromeOS linux beta feature). utf8proc was not installed,
> and the configure failed.
> >
> > This requ
Thanks, Daniel. I didn't realize that option existed, when I hit my
failure. The LZ4 stuff was documented to use --with-lz4=internal, so I went
that route.
On Tue, Dec 3, 2019 at 5:31 PM wrote:
> Author: danielsh
> Date: Tue Dec 3 23:31:42 2019
> New Revision: 1870772
>
> URL: http://svn.apach
On Tue, Dec 3, 2019 at 5:15 PM Greg Stein wrote:
> I was setting up a new chromebook, with a completely barren Ubuntu install
> (using ChromeOS linux beta feature). utf8proc was not installed, and the
> configure failed.
>
> This requirement is not listed in INSTALL.
Good catch! Thank you for r
Julian Foad wrote on Tue, 03 Dec 2019 12:25 +00:00:
> Daniel Shahaf wrote:
> >> Let's start by naming the issues:
> [...]
> >> The semantics I'd like to have are:
> [...]
> > [I] didn't want this issue, while outstanding, to take up any
> > brainwidth.
>
> All sounds good. Thanks for documenting
On 03.12.2019 23:15, Greg Stein wrote:
> Hey all,
>
> I was setting up a new chromebook, with a completely barren Ubuntu
> install (using ChromeOS linux beta feature). utf8proc was not
> installed, and the configure failed.
>
> This requirement is not listed in INSTALL.
>
> I don't know enough abou
Hey all,
I was setting up a new chromebook, with a completely barren Ubuntu install
(using ChromeOS linux beta feature). utf8proc was not installed, and the
configure failed.
This requirement is not listed in INSTALL.
I don't know enough about the use of utf8proc to know whether it *should*
be
On Sun, Dec 1, 2019 at 6:32 PM Daniel Shahaf wrote:
> Nathan Hartman wrote on Sun, Dec 01, 2019 at 10:58:34 -0500:
> > On Thu, Nov 28, 2019 at 4:05 PM Daniel Shahaf
> > wrote:
> > > Y'all might consider starting a wiki page or a jira issue tracking
> > > the categorization. I think it might be
Daniel Shahaf wrote:
Let's start by naming the issues:
[...]
The semantics I'd like to have are:
[...]
[I] didn't want this issue, while outstanding, to take up any
brainwidth.
All sounds good. Thanks for documenting it. Looks like a good little
non-invasive "starter" project for anybody
Daniel Shahaf wrote on Tue, 03 Dec 2019 12:02 +00:00:
>
>
> Let's start by naming the issues:
9. MULTIPLE_TARGETS mode suppresses the "can't show in-repository size
of working copy file '%s'" error. I can't imagine why. If it's fine
to print nothing for a wc file when there are other targe
I just discovered that 'svn info --show-item' has some twisty logic for
_sometimes_ tacking on additional information at the end of a line:
[subversion/svn/info-cmd.c]
1332receiver_baton.multiple_targets = (opt_state->depth >
svn_depth_empty
1333
11 matches
Mail list logo