From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: why is git destructive by default? (i suggest it not be!) Date: Tue, 24 Jun 2008 00:03:52 -0400 (EDT) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: git@vger.kernel.org To: David Jeske X-From: git-owner@vger.kernel.org Tue Jun 24 06:06:07 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KAzmm-0001YP-QE for gcvg-git-2@gmane.org; Tue, 24 Jun 2008 06:05:50 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750937AbYFXEDy (ORCPT ); Tue, 24 Jun 2008 00:03:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750825AbYFXEDy (ORCPT ); Tue, 24 Jun 2008 00:03:54 -0400 Received: from relais.videotron.ca ([24.201.245.36]:25930 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750713AbYFXEDx (ORCPT ); Tue, 24 Jun 2008 00:03:53 -0400 Received: from xanadu.home ([66.131.194.97]) by VL-MO-MR001.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0K2Y00HW38MGA8E0@VL-MO-MR001.ip.videotron.ca> for git@vger.kernel.org; Tue, 24 Jun 2008 00:03:53 -0400 (EDT) X-X-Sender: nico@xanadu.home In-reply-to: User-Agent: Alpine 1.10 (LFD 962 2008-03-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, 24 Jun 2008, David Jeske wrote: > -- Nicolas Pitre wrote: > >> or we expect "running without ever collecting the log" > >> to be a valid mode of operation... which I doubt is the case. > > > > Why not? > > Is see the hole I left in my logic, so let me restate. > > ... or we expect "human parsing of the the log" is a valid common > user-interface for non-git developers. The reflog is one of the primary user interface for all git users. Please just try: git reflog and see for yourself. And if you want more details, then just try: git log -g You may even try any combination of flags in addition to -g with 'git log'. I hope you'll feel much safer then. Nicolas