IETF Logo Mail Archive

Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF

Lars Eggert <lars@eggert.org> Thu, 14 April 2022 06:53 UTC

Return-Path: <lars@eggert.org>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED533A115C; Wed, 13 Apr 2022 23:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUDy2UNPvAhq; Wed, 13 Apr 2022 23:53:25 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E7D13A115B; Wed, 13 Apr 2022 23:53:25 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:a19c:819a:bd55:d9f3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 730112802C1; Thu, 14 Apr 2022 09:53:15 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1649919195; bh=Vfsyp6UehmQwOffT3OYHXr1RpcXMhScd/G1a88u2tUM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=DEx3Xg8Gug7n1NeY/HDT84ZvZG0+VvUk49qHrqs0W9rWk0fNPvU8hFuSzfPq+KC3K ZUCqUhvPtxrSxHtX4z024Cf5nYhmloJzVqyCZxUsib5c7fS4vM0gdC+xwcm0hIhOFh /EkpAYcpWp6ebL/OcXR977RwDYBnEFX4YzXEUedA=
Content-Type: multipart/signed; boundary="Apple-Mail=_2BE1C0E0-7D23-4DF7-B596-4CD225AEC856"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <c9679cee-afa4-f7d4-80a1-83e635d8ad26@gmail.com>
Date: Thu, 14 Apr 2022 09:53:14 +0300
Cc: "Salz, Rich" <rsalz@akamai.com>, Niels ten Oever <mail@nielstenoever.net>, IESG <iesg@ietf.org>, "tao-discuss@ietf.org" <tao-discuss@ietf.org>
Message-Id: <FE38E0F3-C368-42B6-9FD8-2804C38EC7E1@eggert.org>
References: <905c834c-30d7-ede7-6ea1-a5b200a249d7@nielstenoever.net> <45a73c1d-0564-10a6-4243-bf1a209da307@gmail.com> <0C41A5AD-CEFB-4A37-9229-64C03723193F@akamai.com> <c9679cee-afa4-f7d4-80a1-83e635d8ad26@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-MailScanner-ID: 730112802C1.A2355
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/kPvOKRa2ZvBZztwTf43qRavEd9A>
Subject: Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 06:53:30 -0000

Hi,

On 2022-4-14, at 0:08, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 14-Apr-22 01:44, Salz, Rich wrote:
>>>    Not having write access to the repo, it seems I can't issue a PR.
>>     I have a branch and a PR ready to go, with a modest number of minor
>>     fixes, if someone can authorize becarpenter.
>> If that is necessary, it would have to be Neils or maybe Greg.  I don't have any permissions.  I don't think I was "added" to the repository, and I don't recall asking for permission to make a pull request.  You sure?
> 
> I'm sure of nothing when using gh, but GitHub Desktop on Windows told me I had to be authorized to publish a branch and issue a PR. Maybe I'm doing it wrong.

you need to fork the repo and commit your changes to a branch on your fork. Then you can initiate a PR based off that.

Lars

v2.23.0 | Report a Bug | By Email