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=-4.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 4DF861F4C0 for ; Fri, 25 Oct 2019 21:06:44 +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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding; q=dns; s=default; b=hFME7BXzPeGY+tsyuB1xfn4KIJWYfDnTqYI63Frvxs8 GCU7khiIwD3k8EOpWt8Ndqk09hyYojia7Ka4A6NK6BfuA8erhdsahZ12b510L+1X +JTZmhTPashwf3F0t+/+GTml03yJ5oqKpu6fB9Fk5OxUAbY4rT5xhVsClU7WQMn8 = 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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding; s=default; bh=ebmK7O5PQXgZ/uOEcajemk6ybLA=; b=PVAxADQd0meqqIL5T AgsJmVjPTlZhq9LZTTSIs72o9rnIBJidAXrlmlp2vVm6PJHVHHwBUSi265DnbIEX mcb2IWgPZL6NXy9l6tMcsJn2i8VY0wGqUmQf8p29CeGaXyZJCcLyBb6iDlqx2ylG 6RIA7ann8eILfxVWC/fBhPacpI= Received: (qmail 45986 invoked by alias); 25 Oct 2019 21:06: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 45968 invoked by uid 89); 25 Oct 2019 21:06:40 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: us-smtp-delivery-1.mimecast.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1572037596; 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=zqf/nsPsSd+AyHLj1h+CwNPnhEwt5grzXCsUs0yIsJY=; b=SwVpjdB2/vwTO2BzS+fOkWvOfRsC3ukaVfjF5QqEaVMMfDKpM4ic0rhqyTLG7BXGuO0vz6 qKghOa+oyVFmbBp9I/kcikdzyUsg7bq77nW8zQmwF884pn7Rk7IF9JkW73arnR5rauSvlc trs7mPr9qnhE29CeivLbE23t41/zoQY= From: Sergio Durigan Junior To: Joseph Myers Cc: Carlos O'Donell , libc-alpha Subject: Re: Setup non-pushing gerrit instance for glibc. References: <2e93ece9-386b-c587-9355-33a4695a3f02@redhat.com> <875zkcpxpd.fsf@redhat.com> Date: Fri, 25 Oct 2019 17:06:25 -0400 In-Reply-To: (Joseph Myers's message of "Fri, 25 Oct 2019 20:33:33 +0000") Message-ID: <87r230o7qm.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable On Friday, October 25 2019, Joseph Myers wrote: > On Fri, 25 Oct 2019, Sergio Durigan Junior wrote: > >> Unfortunately, you do need to quote the content from the email footer. >> I agree that gerrit should be able to keep track of Message-Id's and >> match the replies using In-Reply-To, but unfortunately it doesn't do >> that. It relies on the information present at the quoted footer to >> determine which change the email refers to. > > If it doesn't work as well as Bugzilla at handling incoming email, it's= =20 > probably not ready for serious use in glibc development (i.e. anyone=20 > submitting patches that way will need to watch for replies on the mailing= =20 > list that don't get into gerrit's data, until gerrit's email handling is= =20 > fixed). Is there an issue for fixing gerrit to handle emails quoting=20 > relevant context without the footer? TBH, I wouldn't know right now. I haven't looked at gerrit's source code to see how hard/feasible it would be to fix this. What we can do is insert a message in the emails explaining that the footer needs to be preserved when replying to it. We will also have to warn the user that replying directly to a new change message will not work; gerrit can only understand email replies to comments. --=20 Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/