IETF Logo Mail Archive

Re: IETF Git and GitHub tutorial

"Salz, Rich" <rsalz@akamai.com> Fri, 11 October 2019 16:00 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE67F120018 for <wgchairs@ietfa.amsl.com>; Fri, 11 Oct 2019 09:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 QwK3bDb5nu1A for <wgchairs@ietfa.amsl.com>; Fri, 11 Oct 2019 09:00:57 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF9A8120013 for <wgchairs@ietf.org>; Fri, 11 Oct 2019 09:00:57 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9BFhCNg017961; Fri, 11 Oct 2019 17:00:56 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=HZDG9BT+uiAKarNA5wNr/+srtiXFvKm+npL48YEE7BI=; b=VuQpAtu5Ybap+z1cnnbW/CJe1JVsNZfp9SvlsCWVSX7uXcOTGAvcxCF+33jOHRak/hhP HjzrBFfD742Dt8CxTro3Ye2D4YwhK63YXLct9lDCIJzJ0FqyhpgO+jtejQA8CtajdUWD c+igCoc7Ja07be6mY8yrCfJ5plESWdHYBoJDCIVcEoIA84C3T6Fk8QtYG//dFuH0j144 2Q7rpfMJIKj+BttnL05aYCStZcijCwY3AVoAFzmXQhJt1TnRLWXhn7OmZWU3yqmI3lE6 XFrmUm8M/lOzC3uTxRvP3F5mH7lCDw+DofKDdBg21IAmxmKVrdKDswRS5zZG/hQFnIjI uA==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2veje9sr3h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 Oct 2019 17:00:56 +0100
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x9BFlVxS027243; Fri, 11 Oct 2019 09:00:54 -0700
Received: from email.msg.corp.akamai.com ([172.27.165.113]) by prod-mail-ppoint5.akamai.com with ESMTP id 2ves59rth4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 11 Oct 2019 09:00:54 -0700
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb4.msg.corp.akamai.com (172.27.165.122) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 11:00:53 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1473.005; Fri, 11 Oct 2019 11:00:53 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Michael Richardson <mcr@sandelman.ca>
CC: IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: IETF Git and GitHub tutorial
Thread-Topic: IETF Git and GitHub tutorial
Thread-Index: AQHVf94ocXH24T/eP02VtwldtknjBqdVXZPQgABwyID//9zHgA==
Date: Fri, 11 Oct 2019 16:00:52 +0000
Message-ID: <4FDDF67C-0E50-43C1-A067-DB4FBD5F453B@akamai.com>
References: <3b3a2e43-3a37-44d8-9967-920d2f977e42@www.fastmail.com> <CADZyTk=7fN+i7H1AX+T7fW3OOQGUAd7z0mtGAeUnpr2O5vZsKA@mail.gmail.com> <CADZyTkkku5y8a1HURp6uQ447eq_dn5wzhwPxhqrpvg1U4dHctQ@mail.gmail.com> <9338.1570802815@dooku.sandelman.ca>
In-Reply-To: <9338.1570802815@dooku.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191003
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.115.130]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3E0A0684324736469A22AAF5190A5DAC@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-11_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=852 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910110144
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-11_09:2019-10-10,2019-10-11 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=830 suspectscore=0 clxscore=1015 adultscore=0 spamscore=0 malwarescore=0 mlxscore=0 impostorscore=0 bulkscore=0 phishscore=0 lowpriorityscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910110144
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/b0zmz8yDdipFAHtkUFe91A0eoFE>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2019 16:01:00 -0000

>    And there is a serious limitation, which is that it pretty much impossible to
    rebase with only the web interface, so after having submitted an edit, once
    it is accepted, one winds up with a tree (fork) you can not use again.
  
The work-around is simple and probably follows what most people do, anyway: do not re-use a branch name for different items of work. (Arguably that's an implied git best practice.) In fact, GitHub pull requests use the branch name, so I would not be surprised if doing this (which you shouldn't) can lead to problems anyway.

v2.23.0 | Report a Bug | By Email