From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jim Meyering Newsgroups: gmane.emacs.devel Subject: Re: use git, not cvs Date: Tue, 10 Jun 2008 13:20:02 +0200 Message-ID: <87wskxzgd9.fsf@rho.meyering.net> References: <20080607125159.8A74F9F05B4@grelber.thyrsus.com> <20080607132037.GA21979@thyrsus.com> <20080607141452.GF1812@muc.de> <20080607152408.GG1812@muc.de> <20080607193747.GB1420@thyrsus.com> <878wxd1sqg.fsf_-_@rho.meyering.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213096835 32122 80.91.229.12 (10 Jun 2008 11:20:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Jun 2008 11:20:35 +0000 (UTC) Cc: esr@thyrsus.com, lekktu@gmail.com, Eli Zaretskii , emacs-devel@gnu.org, Alan Mackenzie To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 10 13:21:15 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K61uc-0006PS-Qc for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 13:21:15 +0200 Original-Received: from localhost ([127.0.0.1]:34240 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K61to-0003q8-WC for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 07:20:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K61tj-0003oc-O1 for emacs-devel@gnu.org; Tue, 10 Jun 2008 07:20:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K61tj-0003oH-CB for emacs-devel@gnu.org; Tue, 10 Jun 2008 07:20:19 -0400 Original-Received: from [199.232.76.173] (port=37650 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K61tj-0003oE-4H for emacs-devel@gnu.org; Tue, 10 Jun 2008 07:20:19 -0400 Original-Received: from smtp3-g19.free.fr ([212.27.42.29]:36297) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K61tX-0005DS-FJ; Tue, 10 Jun 2008 07:20:07 -0400 Original-Received: from smtp3-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp3-g19.free.fr (Postfix) with ESMTP id DF29E17B58A; Tue, 10 Jun 2008 13:20:06 +0200 (CEST) Original-Received: from mx.meyering.net (mx.meyering.net [82.230.74.64]) by smtp3-g19.free.fr (Postfix) with ESMTP id C636B17B56D; Tue, 10 Jun 2008 13:20:06 +0200 (CEST) Original-Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id D8395270EF; Tue, 10 Jun 2008 13:20:02 +0200 (CEST) In-Reply-To: (Miles Bader's message of "Tue, 10 Jun 2008 20:08:55 +0900") Original-Lines: 26 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98859 Archived-At: Miles Bader wrote: > Jim Meyering writes: >> The git repository should never be more than about 30-60 >> minutes behind the CVS one. > > Now if only people would stop committing multiple files in a big change > one-by-one... (it would make the git history a lot more readable) Indeed. To get an idea of what Miles is talking about, compare emacs' gitweb summary with that of say, git itself: http://git.sv.gnu.org/gitweb/?p=emacs.git;a=summary http://repo.or.cz/w/git.git/ Consider how easy it would be to back out a single change in git (where all files in a change set are committed at once) while they're often distributed across two or more commits in emacs. Has anyone tried to establish guidelines for this? It's not just git, of course. No matter what VCS emacs ends up using, establishing a change-set oriented approach in cvs will make the commit log a lot more useful. Many projects encourage use of a single-line summary on line #1 of the commit log, and then any prose/explanation, followed by lines containing the usual ChangeLog-style entries.