Johan Corveleyn wrote on Tue, 05 Dec 2017 00:04 +0100:
> On Mon, Dec 4, 2017 at 11:01 PM, Julian Foad wrote:
> > Johan Corveleyn wrote:
> >> Just thinking out loud here ...
> >
> > [...]> H
> >
> > Now you're over-thinking it. What you said first, what you use at work,
On 05/12/2017 02:38, luke1...@apache.org wrote:
> Author: luke1410
> Date: Tue Dec 5 01:38:11 2017
> New Revision: 1817146
>
> URL: http://svn.apache.org/viewvc?rev=1817146=rev
> Log:
> * site/staging/docs/release-notes/1.6.zh.html: Prefix broken links with
> "XXX (dead link)" so we at least
On Mon, Dec 4, 2017 at 11:01 PM, Julian Foad wrote:
> Johan Corveleyn wrote:
>>
>> [...]
>> Hm, yes, I agree with the "don't write the same thing twice". But
>> perhaps the "general description" above the list of affected files
>> would be a better place:
>
> [...]
>>
>>
Stefan wrote:
Giving some more details about this particular commit:
On 01/12/2017 23:55, luke1...@apache.org wrote:
Author: luke1410
Date: Fri Dec 1 22:55:51 2017
New Revision: 1816926
URL:http://svn.apache.org/viewvc?rev=1816926=rev
Log:
*
Johan Corveleyn wrote:
[...]
Hm, yes, I agree with the "don't write the same thing twice". But
perhaps the "general description" above the list of affected files
would be a better place:
[...]
Though, indeed, we're not required to always have a "general
description", and can just start with
On Mon, Dec 4, 2017 at 3:15 PM, Julian Foad wrote:
> Stefan Sperling wrote:
>>
>> Johan Corveleyn wrote:
>>>
>>> The intention is that the RM doesn't need to go through all the full
>>> log messages in detail, but that he can trust the output of
>>> write-changelog,
Stefan Sperling wrote:
Johan Corveleyn wrote:
The intention is that the RM doesn't need to go through all the full
log messages in detail, but that he can trust the output of
write-changelog, combined with trust in the quality of the log
messages involved.
OK, in that light it all makes sense
On Mon, Dec 04, 2017 at 02:17:59PM +0100, Johan Corveleyn wrote:
> > I believe that whatever we do, somebody will still have to read the full log
> > and check each entry in CHANGES to avoid listing a lot of trivial stuff,
> > and to make sure the most impactful changes appear at the top.
>
> I
On Mon, Dec 4, 2017 at 1:45 PM, Stefan Sperling wrote:
> On Mon, Dec 04, 2017 at 12:16:37PM +0100, Johan Corveleyn wrote:
>> Examples:
>> [U:major] Better interactive conflict resolution for tree conflicts
>> [U:minor] ra_serf: Adjustments for serf versions with HTTP/2
On Mon, Dec 04, 2017 at 12:51:26PM +0100, Stefan Fuhrmann wrote:
> Work on 'svn ls --search' has been completed now,
> release notes and friends have been updated.
>
> -- Stefan^2.
Thank you!
On Mon, Dec 04, 2017 at 12:16:37PM +0100, Johan Corveleyn wrote:
> Examples:
> [U:major] Better interactive conflict resolution for tree conflicts
> [U:minor] ra_serf: Adjustments for serf versions with HTTP/2 support
> [U:client] Fix 'svn diff URL@REV WC' wrongly looks up URL@HEAD (issue
On 29.11.2017 18:40, Paul Hammant wrote:
Thanks for this Marc. I'll go ahead and play with it to learn it capabilities
and (hopefully few) snags.
In 1.10 and for svn:// since 1.9, in-repository authz can be a lot
faster than file-based authz. The reason is that repositories
provide O(1)
On 22.11.2017 14:21, Stefan Fuhrmann wrote:
On 22.11.2017 11:53, Julian Foad wrote:
At the hackathon today we (me, Stefan Hett, Bert, Johan) have been talking
about how to progress 1.10.
We think all the features and changes are safe to release and are not going to
get more testing until
As promised on IRC last Friday, here is a POC implementation of the
"generate changelog from commit messages" functionality, added to
release.py (I'm not very experienced in Python; I mainly depend on
google, SO, copy-paste, ... so don't focus on coding style etc).
This patch is intended to
14 matches
Mail list logo