From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id B34E3385C423 for ; Thu, 6 Oct 2022 16:56:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B34E3385C423 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665075366; 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=Pu92HWYE+NIL0hV+Gty/sfEf9hLIkW6Gwnqq/tvQOyw=; b=DIa3Ek3QbJkRjkRxU9K+DgkBRy0N+AZy4e8vWEeVZCdk8SVxO39p/+gEe+i/E7NRLT5SZg TV0DAAdI5bVvJZ1u0ZE8BKby6k1eC4f5st1HiESg74WeHoP2kAuPddEQYkPTdkgeed175+ QmPix+wzdeGK9VFLTQE04z0uygCeaBc= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-39-EqjAEWkmMoehB2LGPUN3jg-1; Thu, 06 Oct 2022 12:56:05 -0400 X-MC-Unique: EqjAEWkmMoehB2LGPUN3jg-1 Received: by mail-qk1-f200.google.com with SMTP id bl17-20020a05620a1a9100b006cdf19243acso1912515qkb.4 for ; Thu, 06 Oct 2022 09:56:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Pu92HWYE+NIL0hV+Gty/sfEf9hLIkW6Gwnqq/tvQOyw=; b=FgQe7f7SDkbCTyYEJ2pB+SIrsfP/eWKp0Qug1nN2KCEVvi5slv2sf2aw8/ZlOlpGDQ /oYCdCP9Hm+RuKx+BmLzF9RP4Zwomgys2SSP7htH9nkDEq70JcKeKwMt5iLQQ5hXR+GD rC9OLedLFfy8JdmKCpwJJ/sPvX+xC/658GDL7DMQcxOxmMBqcvmhvSBrqAr+iMGmstJA 7uVSKv9xkMfZ6ZyspSsHyoYlbFtzLaOUF7J7U2sLmmTM9+JVKuIwUHAmQYnB8sTyLgHj jv7HK9GorNYe5tUNvdKmiVgN6oUvVTo4Tu5xQ2kcTGP/MdpK06zy2D56TZ0G5xV3fRoy vDiw== X-Gm-Message-State: ACrzQf0PLNXlkONuNbCsAQkAz54KxMLgEd1BqpXfX9RSOnc94zdnt9Hi yAGq7NBRsdC7GJ0hlgozAz9zv+h7tAO4MB1pbRveXHv3QdeUK0TCeo8NOy3sYji30ihIXue4fbK 5ol2Zg0i/0zFDd8LJ3FRpM6pqKqELap6FXg== X-Received: by 2002:a0c:9a0d:0:b0:4b1:982e:96d4 with SMTP id p13-20020a0c9a0d000000b004b1982e96d4mr585717qvd.114.1665075364588; Thu, 06 Oct 2022 09:56:04 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5QB6c3ELxjzk+iscCGnlmCSPEgfQBHA5ubgt6Q8lKz3ba/zhcqbBGA/11FFnz1mDUW+Pq0zvdred26OZTO7dQ= X-Received: by 2002:a0c:9a0d:0:b0:4b1:982e:96d4 with SMTP id p13-20020a0c9a0d000000b004b1982e96d4mr585699qvd.114.1665075364359; Thu, 06 Oct 2022 09:56:04 -0700 (PDT) MIME-Version: 1.0 References: <20220905225046.193799-1-cf.natali@gmail.com> In-Reply-To: From: Jonathan Wakely Date: Thu, 6 Oct 2022 17:55:53 +0100 Message-ID: Subject: Re: [PING 2] [PATCH] libstdc++: basic_filebuf: don't flush more often than necessary. To: =?UTF-8?Q?Charles=2DFran=C3=A7ois_Natali?= Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, 6 Oct 2022 at 17:33, Charles-Fran=C3=A7ois Natali wrote: > > On Thu, Oct 6, 2022, 14:29 Jonathan Wakely wrote: >> >> Sorry for the lack of review. I've been trying to remember (and find) >> some previous discussions related to this topic, but haven't managed >> to find it yet. > > > No worries! > > >> >> The patch does look sensible (and is the same as the one attached to >> PR 63746) so I'll make sure to review it in time for the GCC 13 >> cut-off. >> >> I noticed that you contributed your test case with a FSF copyright >> assignment header. Do you actually have a copyright assignment for GCC >> contributions? If not, you would either need to complete that >> paperwork with the FSF, or alternatively just contribute under the DCO >> terms instead: https://gcc.gnu.org/dco.html > > > > I actually just copy-pasted the header from another test, would it be sim= pler if i just removed it? Yes, that's probably the simplest solution, and then add a Signed-off-by: tag in your patch email, to state you're contributing it under the DCO terms (assuming of course that you are willing and able to certify those terms).