[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Simon Josefsson |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Sun, 19 Feb 2017 10:17:02 +0100 |
User-agent: |
Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux) |
Tim Rühsen <address@hidden> writes:
> On Samstag, 28. Januar 2017 09:37:53 CET Nikos Mavrogiannopoulos wrote:
>> On Fri, 2017-01-27 at 13:24 +0100, Tim Ruehsen wrote:
>> > On Thursday, January 26, 2017 2:07:39 PM CET Nikos Mavrogiannopoulos
>> >
>> > wrote:
>> > > Note that there few small changes from the version you submitted in
>> > > gnutls (one which detects non-ascii chars, and another which allows
>> > > XN-- as prefix).
>> >
>> > Hi Nikos, hi list,
>> >
>> > I am done with coding here (branch 'decode' on jas or rockdaboot) and
>> > now
>> > start reviewing/adding your changes. I'll post my comments /
>> > questions step by
>> > step.
>>
>> Which repository is considered to be the primary? Note that I noticed
>> that the tip of the master in both repos has commits from an unnamed
>> author:
>> Author: userwithuid <address@hidden>
>
> 'jas' is the official repo of Simon. He gave me write access, so I can keep
> this
> and my private repo 'rockdaboot' in sync. Releases are done by Simon - and I
> guess he will review / test all my commits before ;-)
>
> userwithuid made two PRs to repo 'jas' - I reviewed, tested and merged them.
Can we get a name of him or her? Please track contributions in the
AUTHORS file.
/Simon
signature.asc
Description: PGP signature
- Re: providing a libidn compatibility API, (continued)
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/13
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/02/14
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19
Re: providing a libidn compatibility API,
Simon Josefsson <=