From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: emacs.git mirror status Date: Fri, 14 Sep 2007 10:40:36 +0200 Message-ID: <86zlzpr663.fsf@lola.quinscape.zz> References: <87y7f9n06z.fsf@rho.meyering.net> <87sl5hmz2t.fsf@rho.meyering.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1189759291 22150 80.91.229.12 (14 Sep 2007 08:41:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 14 Sep 2007 08:41:31 +0000 (UTC) Cc: Emacs development discussions To: Jim Meyering Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 14 10:41:29 2007 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 1IW6jo-0006IU-Nh for ged-emacs-devel@m.gmane.org; Fri, 14 Sep 2007 10:41:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IW6jo-0007oy-7i for ged-emacs-devel@m.gmane.org; Fri, 14 Sep 2007 04:41:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IW6jA-0007ZJ-47 for emacs-devel@gnu.org; Fri, 14 Sep 2007 04:40:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IW6j7-0007YS-VX for emacs-devel@gnu.org; Fri, 14 Sep 2007 04:40:39 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IW6j7-0007YO-Pe for emacs-devel@gnu.org; Fri, 14 Sep 2007 04:40:37 -0400 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IW6j7-0005Ln-AT for emacs-devel@gnu.org; Fri, 14 Sep 2007 04:40:37 -0400 Original-Received: from quinscape.de (dslnet.212-29-44.ip210.dokom.de [212.29.44.210] (may be forged)) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id KAA09908 for ; Fri, 14 Sep 2007 10:40:34 +0200 X-Delivered-To: Original-Received: (qmail 29955 invoked from network); 14 Sep 2007 08:40:36 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 14 Sep 2007 08:40:36 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 468FA8F8ED; Fri, 14 Sep 2007 10:40:36 +0200 (CEST) In-Reply-To: <87sl5hmz2t.fsf@rho.meyering.net> (Jim Meyering's message of "Fri\, 14 Sep 2007 10\:27\:22 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) X-Detected-Kernel: Linux 2.4-2.6 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:78851 Archived-At: Jim Meyering writes: > dhruva wrote: >> On 9/14/07, Jim Meyering wrote: >>> You can check out a copy of the repository like this: >> >> I have been using it for sometime and hooked to it. Thank you all the >> efforts you have put in to get Emacs on GIT. GIT supports a CVS server >> enabling CVS clients to access the GIT repository. Could this be a >> possible transition plan. > > Yes, it is possible. > However, currently I would not want to allow commit access > through the git cvsserver emulation. IMHO, it is not mature enough. > > Within the next few days, I expect to set up for (read-only) cvs pserver > access to the gnulib git mirror. If that goes well, we'll soon switch > primary upstream development from cvs to git. > > If all goes well there, it should be easy to do the same for emacs. I am afraid that this is not feasible in the current state of affairs: as long as all multi-tty material in the current trunk is only tracked and blamed to a point where Miles was synching rather than the original checkin, one can't seriously work with it. Presumably the information loss is not yet there in the arch repository from Miles, so one needs to either make cvsps understand the arch information present in CVS ChangeLog entries, or import from arch rather than CVS. Of course I am aware that the CVS workflow already _is_ hampered by the information loss, too, but since CVS is rather bad at handling such information anyway, it might not be as apparent. -- David Kastrup