On 04.01.2019 04:33, Troy Curtis Jr wrote:
> Howdy guys,
>
> One of the TODO items I put in the swig-py3 branch README is to provide a
> more useful error message if the user tries to build the swig-py bindings,
> but they are disabled/failed to configure. There are several failure modes
> that wou
Howdy guys,
One of the TODO items I put in the swig-py3 branch README is to provide a
more useful error message if the user tries to build the swig-py bindings,
but they are disabled/failed to configure. There are several failure modes
that would prevent the Python binding from building, however c
Mark Phippard wrote on Thu, 03 Jan 2019 16:36 -0500:
>
> > On Jan 3, 2019, at 4:18 PM, Daniel Shahaf
> > wrote:
> >
> > Mark Phippard wrote on Thu, 03 Jan 2019 15:56 -0500:
> >> Looks good. If we cannot get rid of the iFrame
> >
> > We could replace the iframe by something else, but for the time
>
> On Jan 3, 2019, at 4:18 PM, Daniel Shahaf wrote:
>
> Mark Phippard wrote on Thu, 03 Jan 2019 15:56 -0500:
>> Looks good. If we cannot get rid of the iFrame
>
> We could replace the iframe by something else, but for the time being, ---
Are we still using server-side includes for the navigati
Mark Phippard wrote on Thu, 03 Jan 2019 15:56 -0500:
> Looks good. If we cannot get rid of the iFrame
We could replace the iframe by something else, but for the time being, ---
> can we make the links open in a new window rather than within the iFrame?
Done in r1850269.
Daniel Shahaf wrote:
>> I've committed the scripts, added a cron job, and wired the output
>> into the site:
>>
>> https://subversion-staging.apache.org/docs/release-notes/#upcoming-patch-release
>>
>> I make no claim that the current state is visually pleasing;
Ha ha! It's laugh-out-loud ugly,
On Jan 3, 2019, at 3:40 PM, Daniel Shahaf wrote:
>
> Daniel Shahaf wrote on Thu, 03 Jan 2019 18:50 +:
>> That's a stdin-to-stdout filter that converts the text output to HTML,
>> suitable
>> for inclusion in the Web site.
>
> I've committed the scripts, added a cron job, and wired the outpu
Daniel Shahaf wrote on Thu, 03 Jan 2019 18:50 +:
> That's a stdin-to-stdout filter that converts the text output to HTML,
> suitable
> for inclusion in the Web site.
I've committed the scripts, added a cron job, and wired the output
into the site:
https://subversion-staging.apache.org/docs/r
Daniel Shahaf wrote on Thu, Jan 03, 2019 at 17:38:04 +:
> % ./upcoming.py | tail -46
>
> r1847610 | svn-role | 2018-11-28 04:00:29 + (Wed, 28 Nov 2018)
>
> Merge the r1847181 group from trunk:
>
> * r1847181, r18471
Julian Foad wrote on Thu, Jan 03, 2019 at 17:15:16 +:
> Julian Foad wrote:
> > [...] either inline or links to the verbose text samples above. [...]
>
> More precisely: I propose the output of "svn log" as illustrated in those
> samples,
Here you go.
[[[
% ./upcoming.py | tail -46
--
Julian Foad wrote:
> [...] either inline or links to the verbose text samples above. [...]
More precisely: I propose the output of "svn log" as illustrated in those
samples, concatenated with the full content of the relevant 'STATUS' file.
--
- Julian
Mark Phippard wrote:
> If we did not keep the STATUS file in the branch, then wouldn't it be fairly
> easy
> for anyone to see the info you want just by using svn log?
Look at the manual process I described: it starts with how the user has to
remember the magic incantation for making 'svn log'
On Thu, Jan 3, 2019 at 10:58 AM Julian Foad wrote:
> The itch I'm scratching is this: I want the people who are interested in
> our patch releases, and who read our CHANGES file, to be able to see what
> changes are coming or likely to be coming in the next patch release.
>
> As an example, a few
The itch I'm scratching is this: I want the people who are interested in our
patch releases, and who read our CHANGES file, to be able to see what changes
are coming or likely to be coming in the next patch release.
As an example, a few weeks ago a downstream packager/distributor asked me, "are
Unsubscribing, as requested.
--
- Julian
Gregor Klinke wrote on 2019-01-02:
> Please unsubscribe me!
15 matches
Mail list logo
