From owner-dev-commits-src-all@freebsd.org Sun May 9 10:24:55 2021 Return-Path: Delivered-To: dev-commits-src-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 327B1632F3B; Sun, 9 May 2021 10:24:55 +0000 (UTC) (envelope-from rene@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FdL0R0twNz4rmy; Sun, 9 May 2021 10:24:55 +0000 (UTC) (envelope-from rene@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1620555895; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h65VuM1BgIK/+MD1R+Z5HcUHVmD+RaS/oLDfION3t4c=; b=fPgoblBs85MR/0WqMEnYZdY/YOszeAPTlg/XI+BfJLunxi8z7fZGvu2/R7OlWXxc3rTW8V 0QM//loagCJxEeRT6SJTuoIsZ0nWTSAMbzmfBxZIVkwgjijBNiNvPTBc908jHeZSprFyx1 kKH1AaY7Jdzss9thU8RjRWQJD+jTBNG/riMlIZlq42dAlBGTaTeBFLk4SU2JF/RqjwDxYX cs+8n0OeORegIYhy++WqhVQVJDdPEujDjJOe0atf69VpsuqAJgdcbo/H0NNXdXm2duIG4p dP/5/cFEuMw8vza0dvSQ6dRaEzd1vPMB6/Q36vzwKGod192tZMyryG1VpW4ngA== Received: by freefall.freebsd.org (Postfix, from userid 1185) id F109BAD7A; Sun, 9 May 2021 10:24:54 +0000 (UTC) Date: Sun, 9 May 2021 10:24:54 +0000 From: Rene Ladan To: Alexey Dokuchaev Cc: Pedro Giffuni , Randall Stewart , "src-committers@freebsd.org" , "dev-commits-src-all@freebsd.org" , "dev-commits-src-main@freebsd.org" Subject: Re: git: 5a4333a5378f - main - This takes Warners suggested approach to making it so that platforms that for whatever reason cannot include the RATELIMIT option can still work with rack. It adds two dummy functions that rack will call and find out that the highest hw supported b/w is 0 (which kinda makes sense and rack is already prepared to handle). Message-ID: References: <202105072134.147LYjPn018824@gitrepo.freebsd.org> <4b297976-4b06-33a8-b390-18c01561b463@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1620555895; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h65VuM1BgIK/+MD1R+Z5HcUHVmD+RaS/oLDfION3t4c=; b=hexIy5WipFgKUPIHZBQD+YGF7vugeOZCLKGts/+7Q2Bv9IjlVypGi4mdNyw8PTOmgebDMB Yb5qqFlDFmeRAL3ua/pkWVpcKkq3T28qiYJqkksySyNcJG7iOCDihUxUuc+GveoChvkaZh fc3LAehTll4azDy9lMxuDd9w5qQ1uGUJmvqcL3wfCYfVv8sBAP1PSskwqrOeef3opEMmKl 7Tgurymxb+wSIKbp9T6Q6z7y0bvsJd60vpRX3d0YVuzOYdINZJ+Yh/ITLNtTiAzvFAm2Fr ghCza9n1sLRB4ZcsBtVZcKuklcjPoHrnzoP+R+k5jk6xq0Xu0FXzUXoZS1xyfw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1620555895; a=rsa-sha256; cv=none; b=bjhlv/6n1R2R4FYn0Map4lTiJ0I3pdOemZKMo6Rhb/Bgj5hYc88SWR7DdeykC+O//thT/6 5mB5m2LLKzkT7CZw7gQOztWXl3fGMc1A0D/aEIoe5VicYWx2qtpanhbZsnT08wYd5X8cQM Ge7kpQW1XWHm2ze5k5QF24Pvihtb3Nqt1kHAiVGqtKN0RRFt1jEZIXDBIwFOYdYaZHKJPu ToOHuZCW6ugLLIfUo0Zvl4S/ZoFKYJPllNw9xSKmVpeRx8oxmof8zqLszgj3qrySdN6PpX /BgPvirthHLb3a66p76anAolWAL5n7DqWfw8R5diAlPaNaJHo+3n0vJzdkIntA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: dev-commits-src-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the src repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2021 10:24:55 -0000 On Sat, May 08, 2021 at 07:05:16AM +0000, Alexey Dokuchaev wrote: > On Sat, May 08, 2021 at 12:22:24AM -0500, Pedro Giffuni wrote: > > ... > > +1 even in git this breaks the shortlog in ugly ways. > > Someone(tm) should probably file an issue at their upstream, as ignoring \n > and only stopping at \n\n for short log definitely looks like a bug to me. > No, because shortlog looks at the first paragraph, not the first sentence. René