From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs is on Bazaar now. Date: Mon, 28 Dec 2009 13:08:57 +0100 Message-ID: References: <87d4206n80.fsf@canonical.com> <87637r610w.fsf@red-bean.com> 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 1262002253 11977 80.91.229.12 (28 Dec 2009 12:10:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2009 12:10:53 +0000 (UTC) Cc: kfogel@red-bean.com, Andreas Schwab , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 28 13:10:46 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 1NPEQv-0007ng-89 for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2009 13:10:45 +0100 Original-Received: from localhost ([127.0.0.1]:52503 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPEQv-00061s-JS for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2009 07:10:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPEPb-00059N-Is for emacs-devel@gnu.org; Mon, 28 Dec 2009 07:09:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPEPX-00056P-7o for emacs-devel@gnu.org; Mon, 28 Dec 2009 07:09:23 -0500 Original-Received: from [199.232.76.173] (port=48898 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPEPW-00056J-Op for emacs-devel@gnu.org; Mon, 28 Dec 2009 07:09:18 -0500 Original-Received: from mail-bw0-f215.google.com ([209.85.218.215]:36651) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPEPW-0002ra-HP for emacs-devel@gnu.org; Mon, 28 Dec 2009 07:09:18 -0500 Original-Received: by bwz7 with SMTP id 7so7170751bwz.26 for ; Mon, 28 Dec 2009 04:09:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=r6nU+OTyNnzwHaUNEDQdBIQQbdvj0vieomo1OlX2dh0=; b=ZY0ADHUCboMvY0yaxPflzecJqNdc2XAxI7kTf4XONFnAMTmECck83DbBkqu6P+QUJ6 /ii/saKCPYVLmpStRZe32bCdsmpuH5BX5bm0ThkDVnaYLlQzoKtLUXIIW8iLvBgyOl/Z 7GD/3JHc+m3WTjPY+gWGhk0Alio6tQ/i6alzk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=ELuKd2vXcDkcYm1j0DukxWx2G4e13HMeiEEmf/XAzgmyom/3MnHt/pigBRQtQcko0r Q7DOL0zpktfIChKRLcgcxLK6mjP95xg1yqJrV2PU9a6kjxlRZNbsoqKN1KDwHT2r0e+H hhCpLPGt5QVcOvJLM4ewUp3DNB6rSejDceEk8= Original-Received: by 10.204.156.203 with SMTP id y11mr4074186bkw.200.1262002157295; Mon, 28 Dec 2009 04:09:17 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:118863 Archived-At: On Mon, Dec 28, 2009 at 12:45, Kenichi Handa wrote: > Now with bazaar, according to the wiki page, it seems that I > must commit all files at once with a single log, and thus > all changed files are given the same log. =C2=A0Is that true? =C2=A0Is > that the right thing? Yes. > If so, is there any convention about the format of the log? > Can I use a relevant part of ChangeLog file as is? Yes, but it is useful to start the commit log with a one-line description of the changes, because there are commands to show the commits with their comments in "single line mode". For example, I committed a change for vc-git, and the ChangeLog entry was this: 2009-12-28 Juanma Barranquero Supersede color.diff settings in git log (bug#5211). * vc-git.el (vc-git-print-log): Pass "--no-color" to log to avoid escape chars in its output when the user has color.diff set to `always'. This fix works on git 1.4.2 and newer (released on 2006-08-13). For the commit message I uses just the first line, but for more extensive changes I would've used the whole ChangeLog entry. Now, using "bzr log -l10 --line", you get: 99201: Juanma Barranquero 2009-12-28 [merge] Supersede color.diff settings in git log (bug#5211). 99200: Juanma Barranquero 2009-12-28 [merge] Update .bzrignore. 99199: Juanma Barranquero 2009-12-28 Update autoload checksum. 99198: Karl Fogel 2009-12-27 [merge] Merge: update nt/INSTALL for CVS->Bazaar switchover too. 99197: Karl Fogel 2009-12-27 [merge] Merge: document that we are on Bazaar = now. 99196: Andreas Schwab 2009-12-27 Add .bzrignore 99195: Chong Yidong 2009-12-27 * minibuf.c (Fall_completions): Minor optimization. 99194: Kevin Ryde 2009-12-26 * man.el 99193: Kevin Ryde 2009-12-26 (Man-bgproc-sentinel): When "-k foo" produces no output show error 99192: Kevin Ryde 2009-12-26 Tweak a comment: it's man-db on gnu/linux which agrees with posix that Juanma