From owner-svn-src-all@freebsd.org Thu Jan 17 22:43:31 2019 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FCD01482623; Thu, 17 Jan 2019 22:43:31 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com [209.85.166.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE68989082; Thu, 17 Jan 2019 22:43:30 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f176.google.com with SMTP id m62so4072615ith.5; Thu, 17 Jan 2019 14:43:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=0Ie4QDBR9bkWLCtsoaBF64uD85dS5Hw31mojuNcIinQ=; b=ntiFCRzuK/nCJsBmOhocOwh2Ps78nK2O0WPQJlKp3bdmVr2YIM19OuQGRDlJeeHcXA UD7KWgKCr6PtoE9J2QZXFTwKXJfKF+Vv1yG9ouqofB/43nBtcTb3GlDkg2derVGQJ7hE 6eI5tpTsn+ooku8N8rS1Jil8Pq24YhW35yl5mggf5no+tOXH5qmQF/W2BYUFiyO2PU6m Fr0AL9TVT0j/6+UPcEeVaA6R1o/79Yk1uPnRB5qnaqoi8oSaLRd3ZrWApr6/yVt2hEFl J+y3SOIh8Y2GeFRHSDkc5usR9x9bS6KGxqc/Lt8OT1BB3O1sgrEA3uZ1H9lsosa/CKZN rETA== X-Gm-Message-State: AJcUukfxJC5EYiOtc4x7vEMD/9LQCRLUcyAaLc1dsWR/6RW7lS/rcUWo vF1mHZSvynwQipjcKmsyBgMPQe3+ X-Google-Smtp-Source: ALg8bN46bsSikaFfJRk5wUSPBE45S7K3Wep/WWDv6YG5p/jGhqofcVmqlu+WtqP/WRGK9T3bBAhufg== X-Received: by 2002:a24:2104:: with SMTP id e4mr9090720ita.59.1547761548205; Thu, 17 Jan 2019 13:45:48 -0800 (PST) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com. [209.85.166.49]) by smtp.gmail.com with ESMTPSA id y5sm940866ioj.9.2019.01.17.13.45.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Jan 2019 13:45:47 -0800 (PST) Received: by mail-io1-f49.google.com with SMTP id b23so9062063ios.10; Thu, 17 Jan 2019 13:45:47 -0800 (PST) X-Received: by 2002:a6b:6111:: with SMTP id v17mr9388524iob.107.1547761547775; Thu, 17 Jan 2019 13:45:47 -0800 (PST) MIME-Version: 1.0 References: <201901171808.x0HI80jC068564@repo.freebsd.org> <2d239dc0-915c-2d2b-0936-a40af5e9ead9@freebsd.org> In-Reply-To: <2d239dc0-915c-2d2b-0936-a40af5e9ead9@freebsd.org> Reply-To: cem@freebsd.org From: Conrad Meyer Date: Thu, 17 Jan 2019 13:45:36 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: svn commit: r343118 - in head/usr.sbin: . trim To: Eugene Grosbein Cc: src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: BE68989082 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.97)[-0.974,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 22:43:31 -0000 On Thu, Jan 17, 2019 at 1:16 PM Eugene Grosbein wrote: > > 18.01.2019 3:23, Conrad Meyer =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > Please back it out; stop attributing code review to "hackers@," which > > can not (it's a list, not individuals) and did not review this > > changeset; and put it on phabricator for actual review. > > There is already https://reviews.freebsd.org/D18380 by imp > and there were over 6 weeks since it had an update. > Newly committed code has most of its changes. Your response does not address *any* of the above concerns. It's just unrelated. The review you linked to isn't one you submitted for this change; it's Warner's, and that one stalled because you were such a jerk to him last time that he needed time off from you. If you want to socialize, revive, or expedite someone else's review, maybe add a new comment to the review, or post a discussion hackers@, or something like that. You still can't attribute code review to hackers@, especially as no such review happened. Conrad