From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 343 invoked by alias); 10 Oct 2013 13:22:26 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 32766 invoked by uid 89); 10 Oct 2013 13:22:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Oct 2013 13:22:26 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r9ADMLaw006953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 Oct 2013 09:22:22 -0400 Received: from barimba (ovpn-113-128.phx2.redhat.com [10.3.113.128]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r9ADMJI5010489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Oct 2013 09:22:20 -0400 From: Tom Tromey To: Joel Brobecker Cc: Binutils Development , GDB Development Subject: Re: src.git test repository References: <87y565m7ma.fsf@fleche.redhat.com> <87r4bu9mw3.fsf@fleche.redhat.com> <20131010051314.GI3066@adacore.com> Date: Thu, 10 Oct 2013 13:22:00 -0000 In-Reply-To: <20131010051314.GI3066@adacore.com> (Joel Brobecker's message of "Thu, 10 Oct 2013 09:13:14 +0400") Message-ID: <87eh7t9s6s.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-10/txt/msg00041.txt.bz2 Joel> There will be issues with special-feature development branches, however. Joel> Let's say, for instance, that people want to collaborate on a certain Joel> feature, and use a branch for its development. If development takes Joel> a while, they might want to do regular merges from HEAD... We can adjust Joel> the rule to say that merges are verbotten except on branches whose name Joel> is prefixed by Eg. "topic/". Perhaps just prohibiting them on master is enough? Joel> - we seem to be getting one email per push, instead of one email Joel> per commit? I checked, and yeah, this is what happens. I think I can change that, if you want. Joel> - Style check the revision log to forbid commits if the second Joel> line (line after subject) is not empty. I have found that Joel> this assumption is too ingrained everywhere in git, and that Joel> not respecting it makes things look bad. While I agree that we ought to adopt a more git-ish commit style, this goes against my early plan of making as few "extra" change to our processes as possible. I was leaving all non-essential change proposals for later, to avoid complicating the switchover. I guess if enough people +1 the idea I will do it. Tom