From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Sun, 22 Nov 2009 21:09:19 -0600 Message-ID: <87ocmu7x9c.fsf@red-bean.com> References: <87vdhfpil2.fsf@red-bean.com> <87einvxy9c.fsf@red-bean.com> <20091118230952.GB908@muc.de> <87my2jw05z.fsf@red-bean.com> <83skc9pbf7.fsf@gnu.org> <87iqd5vw5n.fsf@red-bean.com> <877htl53tc.fsf@telefonica.net> <87ws1ku7zd.fsf@red-bean.com> <87hbso4s13.fsf@telefonica.net> <83aaygoy90.fsf@gnu.org> <87vdh36d48.fsf@telefonica.net> <831vjrptha.fsf@gnu.org> <87einr63b6.fsf@telefonica.net> <83y6lzo9e7.fsf@gnu.org> <871vjr750o.fsf@uwakimon.sk.tsukuba.ac.jp> <83tywnnq34.fsf@gnu.org> <873a475bsr.fsf@telefonica.net> Reply-To: Karl Fogel NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1258945782 16241 80.91.229.12 (23 Nov 2009 03:09:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Nov 2009 03:09:42 +0000 (UTC) Cc: =?utf-8?Q?=C3=93scar?= Fuentes , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 23 04:09:35 2009 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 1NCPJ0-00017M-Lf for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 04:09:34 +0100 Original-Received: from localhost ([127.0.0.1]:33649 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCPJ0-0001wx-1w for ged-emacs-devel@m.gmane.org; Sun, 22 Nov 2009 22:09:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCPIv-0001wB-Bd for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:09:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCPIq-0001qi-GE for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:09:28 -0500 Original-Received: from [199.232.76.173] (port=35043 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCPIq-0001qf-BI for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:09:24 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.206.141]:53881) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NCPIo-00053L-9D; Sun, 22 Nov 2009 22:09:22 -0500 Original-Received: from localhost ([127.0.0.1]:53604 helo=kfogel-work ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.69) (envelope-from ) id 1NCPIn-0001HI-43; Sun, 22 Nov 2009 21:09:21 -0600 In-Reply-To: (Richard Stallman's message of "Sun, 22 Nov 2009 21:28:58 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/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:117547 Archived-At: Richard Stallman writes: > They are not equivalent. The ChangeLog files are included in the > checkout, so you can read them even when you are offline (which is > nearly all the time, for me). `bzr log' requires contact with the > repository. Yes, but the repository is local too! There are possible setups in which a repository might be non-local, but I hope we won't be recommending any of those for Emacs. In all the bzr setups I use, logs and other history information are available locally. This is the normal way to use distributed version control systems, not just bzr. By the way, 'bzr log --gnu-changelog' will print the log information in ChangeLog format. > Is there a way to get all the information about what has been > merged into the current trunk? Yes: $ bzr log -n0 Actually, make that: ### unplug your network cable... $ bzr log -n0 ### ...watch it work anyway :-) > Various directories have separate ChangeLog files. Is that true also > for `bzr log', or is it one log for the whole package? One log for the entire "package" ("branch", in bzr terminology). You can specify subdir arguments, if you only want the logs for those subdirs. > Another convenience with ChangeLog files is that we split them into > manageable-size parts. It would be nice to have a script that would > do the same thing to the output of `bzr log', preferring to split > at the points where releases occurred. Just use the -r flag to show only logs in a certain date range. (A script could do that, with the dates set to release dates, of course.) -Karl