[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-dev] Merging Tor Bug #27490

To: tor-dev@xxxxxxxxxxxxxxxxxxxx, teor@xxxxxxxxxxxxxx
Subject: [tor-dev] Merging Tor Bug #27490
From: "Neel Chauhan" <neel@xxxxxxxxx>
Date: Thu, 29 Nov 2018 00:23:16 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 28 Nov 2018 19:31:02 -0500
List-archive: <http://lists.torproject.org/pipermail/tor-dev/>
List-help: <mailto:tor-dev-request@lists.torproject.org?subject=help>
List-id: discussion regarding Tor development <tor-dev.lists.torproject.org>
List-post: <mailto:tor-dev@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-dev@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-dev" <tor-dev-bounces@xxxxxxxxxxxxxxxxxxxx>

Hi,

I noticed that while you all have accepted bug #27490 (When ClientPreferIPv6ORPort is set to auto, and a relay is being chosen for a directory or orport connection, prefer IPv4 or IPv6 at random), it has not been merged. Is there anything I can do to speed up the process since I also have code ready for #27491 and #27492 but am awaiting the merger of #27490 before I submit them?

I am also currently working on Bug #27647.

Thank You,

Neel Chauhan
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Follow-Ups:
- Re: [tor-dev] Merging Tor Bug #27490
  - From: teor

Prev by Author: [tor-dev] How does Tor plan to deal with HTTP/3 (HTTP over QUIC)
Next by Author: [tor-dev] Whitepaper draft: Towards Side Channel Analysis of Datagram Tor vs Current Tor
Previous by thread: [tor-dev] New sbws milestones on trac
Next by thread: Re: [tor-dev] Merging Tor Bug #27490
Index(es):
- Author
- Thread