From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar?= Fuentes Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Mon, 23 Nov 2009 04:09:56 +0100 Message-ID: <87zl6egcmz.fsf@telefonica.net> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1258945927 16540 80.91.229.12 (23 Nov 2009 03:12:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Nov 2009 03:12:07 +0000 (UTC) Cc: 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:12:00 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 1NCPLL-0001jr-Rl for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 04:12:00 +0100 Original-Received: from localhost ([127.0.0.1]:58171 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCPLK-0003vE-Nk for ged-emacs-devel@m.gmane.org; Sun, 22 Nov 2009 22:11:58 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCPLG-0003ur-9b for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:11:54 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCPLB-0003t8-Lp for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:11:54 -0500 Original-Received: from [199.232.76.173] (port=35072 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCPLB-0003t2-GP for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:11:49 -0500 Original-Received: from impaqm3.telefonica.net ([213.4.138.3]:23023) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCPLB-0005LF-1d for emacs-devel@gnu.org; Sun, 22 Nov 2009 22:11:49 -0500 Original-Received: from IMPmailhost6.adm.correo ([10.20.102.127]) by IMPaqm3.telefonica.net with bizsmtp id 8RN81d00f2kvMAa3PTBnHJ; Mon, 23 Nov 2009 04:11:47 +0100 Original-Received: from qcore ([83.40.117.83]) by IMPmailhost6.adm.correo with BIZ IMP id 8TBl1d00E1o2LpP1mTBmSY; Mon, 23 Nov 2009 04:11:47 +0100 X-TE-authinfo: authemail="981711563$telefonica.net" |auth_email="981711563@telefonica.net" X-TE-AcuTerraCos: auth_cuTerraCos="cosuitnetc01" 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: Genre and OS details not recognized. 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:117548 Archived-At: Richard Stallman writes: > BTW, one thing that the people who only have experience with CVS does > not appreciate, is a changeset-oriented VCS, where the source base > transforms on discrete and well defined steps. Among other things, th= is > makes the Changelog unnecessary, as it turns to be the equivalent of > `bzr log'. > > 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. Unless you explicitly request it, a bzr branch or checkout carries the full history of the branch. So `bzr log' does not need contact with the repository. A bzr branch in your machine carries all version control data that you could get from the CVS server for that branch. > The obvious solution, running `bzr log' and saving output to a file > with every update, is not a full solution since it won't give the real > information about branches that were merged. > > Is there a way to get all the information about what has been > merged into the current trunk? Yes: bzr log -n1 You can even see the history of the branches that were merged into the branches that were merged into the branches [repeat n times] that finally were merged into trunk: bzr log -n0 And everything without net access. > Various directories have separate ChangeLog files. Is that true also > for `bzr log', or is it one log for the whole package? bzr log elisp will show the log of the subset of the history that touches files on the elisp directory, for instance. This works for all files and directories. > 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. You can ask to see the log between two points. A point can be a revision number or a tag. bzr log -r tag:sometag.. shows the log from the tag `sometag' to the last revision. --=20 =C3=93scar