From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 174D41F463 for ; Mon, 30 Sep 2019 19:41:43 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=VqtQN u9eY3PCgdgYV6XepaTCXgV1jf/r8/k+iUDAitkzrBJ4js5H47q06M3opBFl82lJw kR1PINMGpiAoadh08NasUvTCLD3TXnXnvU0w7LPienWPbAYkqm1TzZRNGMuNBmU7 d1gfHdBbVzuPo/8lmq1vDGthp1VVBoMgdj3jSo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=nyMwU46Dota UgdUpWvD7Uj5gVhs=; b=XFoqkDCMGymatA9oU2YFlaKptZ5RIB8GOkxJj3qrNWc MOg7fMws46rgJw9O1DAX4AfAbwBfODpgavMCTgvmy5UhUZCfaPrHytWnhNjzfxnS y/5POv/FZQoPZvsKccQygJ1zL5QuCZBMTzc0+Os9TdllyHSOkgzMSrFmr67jNcNo = Received: (qmail 16552 invoked by alias); 30 Sep 2019 19:41:41 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 16544 invoked by uid 89); 30 Sep 2019 19:41:40 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: esa4.mentor.iphmx.com IronPort-SDR: jfeaJjK8GczI7zfdix85K+dovq8vo74ZAT2z3jmhASC2dtmpygtPkMt6ensGlRZkEb22QCg166 9Q2/T/9lEZEiOEXG6SYgp/kXAejMtqtRzz6Rz5aRZ/8FTdFt7fRSxPcHIrm1E0uabujsJx8PxL +lyBVw3CCFONLilCqmIUmNdx+GtK/7teMgrbXSVYP7NuvySbbkypq4fpUSe6N4Gw4UlByNyxCx K/s9qfMaQPjpYpM5Y6JUNWZt9clC18ySPWDmxr+NjLHx7GWQdCHSbDp+Gjk+5XUpXmrmkCI8MF jRU= IronPort-SDR: ZoYM1TJdvfAfwC59sAkzIbzhax8umdznnpO6cX8u4pqd2mZMlIY7vc/KFIR0Y/vwz0zwg48kOM r/nOklkWCC6iPpNTR73fVH6oYOqjl3sFHn7d4QI0lItHaq+v6N6PMelq9gWQh4twrR9KiHh4Nk Msu23v58svamepgCML3p23MfVpCCb31pF2srJFdvJtzp4YwO4s78mFvi5vTnWvN2xcE+65SC1M kBTXDFnwTfjWsaEkJvQv36Qb02eJh5Td5RN0Q2eq7LU8gH9WVg8a9L6aBt1MsZnDR/rPwGDbbv wTY= Date: Mon, 30 Sep 2019 19:41:32 +0000 From: Joseph Myers To: Florian Weimer CC: Siddhesh Poyarekar , Carlos O'Donell , Adhemerval Zanella , Subject: Re: When can we stop writing ChangeLogs? In-Reply-To: <87ftkdzl4v.fsf@oldenburg2.str.redhat.com> Message-ID: References: <6ebd0e52-a18f-15fc-f4ab-cf2c3afc74e9@gotplt.org> <3bd4b069-e16b-af68-fb2f-17d2458bece5@redhat.com> <878sq522xz.fsf@oldenburg2.str.redhat.com> <52634368-ee1e-23d1-1d61-de0057e03829@gotplt.org> <87ftkdzl4v.fsf@oldenburg2.str.redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-1152306461-450472880-1569872492=:1462" ---1152306461-450472880-1569872492=:1462 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT On Mon, 30 Sep 2019, Florian Weimer wrote: > I'm looking for something far simpler here—a script that submitters and > reviewers can run to see what's going to be committed, and some level of > project consensus that this is how patches should be posted. I suggest that should be "git am", as an existing known format for email patch submissions, for any case except where the patch has already been committed (and really "git am" format could probably be used there as well), the patch would be excessively large (whether because of large generated files or otherwise) or the patch contains mixed character sets which require it to be attached in compressed form to avoid it being mangled. We can discuss details regarding e.g. scissors lines, but I think we should still aim for patch submissions that are valid for "git am" in some form - and in particular, that use "git am" markings to separate the commit message from other remarks (e.g. differences between revisions of the patch) that are not intended as part of the commit message. -- Joseph S. Myers joseph@codesourcery.com ---1152306461-450472880-1569872492=:1462--