From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: merging emacs-24 Date: Fri, 28 Nov 2014 17:14:57 +0200 Message-ID: <831tonmk5q.fsf@gnu.org> References: <87a93eavwt.fsf@lifelogs.com> <87wq6hap7v.fsf@lifelogs.com> <87k32hrdj5.fsf@engster.org> <87vbm0a6zv.fsf@engster.org> <8361e0o7ee.fsf@gnu.org> <87fvd4trzx.fsf@igel.home> <831tooo576.fsf@gnu.org> <87k32ga3dh.fsf@engster.org> <877fyg9t8y.fsf@engster.org> <87r3wo5ftl.fsf@lifelogs.com> <83r3wnn3bq.fsf@gnu.org> <87a93bxufn.fsf@fencepost.gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1417187736 13480 80.91.229.3 (28 Nov 2014 15:15:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Nov 2014 15:15:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 28 16:15:27 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XuNGZ-0007Ur-BW for ged-emacs-devel@m.gmane.org; Fri, 28 Nov 2014 16:15:27 +0100 Original-Received: from localhost ([::1]:44866 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XuNGY-0004kT-Sm for ged-emacs-devel@m.gmane.org; Fri, 28 Nov 2014 10:15:26 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50385) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XuNGH-0004dw-Sb for emacs-devel@gnu.org; Fri, 28 Nov 2014 10:15:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XuNGC-0001kt-N8 for emacs-devel@gnu.org; Fri, 28 Nov 2014 10:15:09 -0500 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:49385) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XuNG6-0001bC-8k; Fri, 28 Nov 2014 10:14:58 -0500 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NFR002008HCZB00@mtaout29.012.net.il>; Fri, 28 Nov 2014 17:12:52 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NFR003NW8XG8Q10@mtaout29.012.net.il>; Fri, 28 Nov 2014 17:12:52 +0200 (IST) In-reply-to: <87a93bxufn.fsf@fencepost.gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:178425 Archived-At: > From: David Kastrup > Date: Fri, 28 Nov 2014 15:37:32 +0100 > > Eli Zaretskii writes: > > >> From: Ted Zlatanov > >> Date: Thu, 27 Nov 2014 19:28:22 -0500 > >> > >> One request: maybe it could log what it does, especially the shell > >> commands, a little better. > > > > It's actually something I sorely miss in Git itself: a full log of all > > commands. Bazaar has ~/.bzr.log, which over the years was invaluable > > for tracking past problems and also my own mistakes (and mistakes made > > by others) in using the tool. I hope Git will get such a feature, or > > maybe it already does. > > Have you tried "git reflog" ? I'm actually using it all the time. It's a misunderstanding if you think "git reflog" is the answer to what I'm looking for. ~/.bzr.log shows: . every bzr command, including the date/time when it was issued . every message displayed by every command on the console, including for example received/transmitted statistics . additional messages, such as the branch on which the command was working . every error message, including Python backtrace . for pull/update/merge commands, the list of changes in the same format used by "bzr status" and "git status --short" . each record comes with a time stamp relative to the time the command was invoked In addition, bzr automatically roll over the log file when it gets too large.