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.0 required=3.0 tests=AWL,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 31A8D1F4C1 for ; Fri, 25 Oct 2019 10:21:21 +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:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-type:content-transfer-encoding; q=dns; s=default; b=Vg+hCWLCNOAWvG9FvvS8/sCSUpUFpv/lN/S/vvt2Tyc l2S2zxVzsA4OXwk/9igtcop1q4bX1nILgG7Sl4e9xWsgnqKslxeEvToF1elrGudw qE9/eXi7SD1yo+yWh7X9feYbO923THzJDtNX0arISykAnf0HO9BEZNR5FlEQw6Xs = 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:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-type:content-transfer-encoding; s=default; bh=tXPWSn96JvhPpKw7JveXA3wP/Pc=; b=G1TVs7Y/0JZL01fGV KJsD2xmtf2tZy71Q/Gq6nJV7gWVI5O+/Qs8RM+YvEPRk0j+3VZv+0oBaCb61TnPL 8bGKrO4Nktevl3szO6qrC8VU/qyhghdiSZu6lZjPvnaZhcUgICIkD7SJYTkflOp0 O5GDU0SYSly666i6N0TGZYDJ58= Received: (qmail 112419 invoked by alias); 25 Oct 2019 10:21:18 -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 112410 invoked by uid 89); 25 Oct 2019 10:21:17 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: us-smtp-1.mimecast.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571998874; 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=/pphAuxio6++vUngIAV7GNxQPheYSmGcErBT36D+tYg=; b=HIhRcTAW78Md7cbrG+fatEOHSpvvEYaKJgYFG/Xfqssc1pC47utsUJL+ouGQJ7LTcPvVZT hqRm2PMA6KEXAq2l+ufoZYLwt5qlKyotni2JOhB9/GRrKYKq9HVn8fMh8P8yvNTLZs/VCu yk15QbBb+lGEW0H/PavbVFBEAjYuh+A= Message-ID: <33f6c4e78dc50ce38fffbb4a30bc4874f75ff191.camel@redhat.com> Subject: Re: Setup non-pushing gerrit instance for glibc. From: Ian Kent To: Jonathan Nieder Cc: Joseph Myers , Carlos O'Donell , libc-alpha Date: Fri, 25 Oct 2019 18:21:06 +0800 In-Reply-To: <20191025011641.GA45423@google.com> References: <2e93ece9-386b-c587-9355-33a4695a3f02@redhat.com> <580baf4ff0699a1eed12c2ea48f2162db639ad1c.camel@redhat.com> <20191025011641.GA45423@google.com> User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 2019-10-24 at 18:16 -0700, Jonathan Nieder wrote: > Hi, >=20 > Ian Kent wrote: >=20 > > I haven't spent much time with Gerrit but the time I have spent > > I've found myself thinking Gerrit is designed with the assumption > > that submissions are "one" patch. > >=20 > > I found handling a patch series (which I almost always have when > > doing changes) rather painful! >=20 > Interesting. The Gerrit project itself[1] uses Gerrit and very often > uses patch series. See [2] for an example. >=20 > The section in its documentation on "developing multiple changes in > parallel"[3] (admittedly poorly named) says a little more about this. Right, and I have managed to get a couple of multi-patch changes through the Gerrit review process in the past but I found it very difficult to find out how to achieve it and I expect the same thing will happen again next time I need do it. This likely isn't a problem for people that use Gerrit on a day to day basis (once familiar with the processes). So I guess my point is that something specific for new adopters is needed in the documentation, but of course I could be just plain thick so maybe it's not worth worrying about, ;) I also haven't looked at the links you provided so maybe I making noise about nothing at all, OTOH those likes look a bit familiar ... >=20 > Thanks and hope that helps, > Jonathan >=20 > [1] https://gerrit-review.googlesource.com/ > [2] https://gerrit-review.googlesource.com/c/gerrit/+/208641 > [3]=20 > https://gerrit-review.googlesource.com/Documentation/intro-user.html#mult= iple-features