From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: Reverting an uncommitted revert Date: Wed, 20 May 2009 14:25:20 -0400 (EDT) Message-ID: References: <4A136C40.6020808@workspacewhiz.com> <20090520032139.GB10212@coredump.intra.peff.net> <025225A0-FACC-4A29-A747-40201A7FBA19@wincent.com> <20090520141709.GO30527@spearce.org> <7vab57zmd8.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: "Shawn O. Pearce" , Wincent Colaiuta , Jeff King , Joshua Jensen , git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Wed May 20 20:26:53 2009 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 1M6qV8-00024V-0y for gcvg-git-2@gmane.org; Wed, 20 May 2009 20:26:50 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756729AbZETSZe (ORCPT ); Wed, 20 May 2009 14:25:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756704AbZETSZd (ORCPT ); Wed, 20 May 2009 14:25:33 -0400 Received: from relais.videotron.ca ([24.201.245.36]:18482 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756666AbZETSZ2 (ORCPT ); Wed, 20 May 2009 14:25:28 -0400 Received: from xanadu.home ([66.131.194.97]) by VL-MH-MR001.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KJY008H7GI87082@VL-MH-MR001.ip.videotron.ca> for git@vger.kernel.org; Wed, 20 May 2009 14:25:20 -0400 (EDT) X-X-Sender: nico@xanadu.home In-reply-to: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Wed, 20 May 2009, Nicolas Pitre wrote: > On Wed, 20 May 2009, Junio C Hamano wrote: > > > (3) What should happen when you cannot write the index out as a tree? I > > think it is easier to make mistakes during a conflicted merge > > resolution than during a straight linear development of your own, and > > one of the cases that would benefit most would be that you have > > resolved a path to your satisfaction but then later you screw up > > while resolving some other paths, losing an earlier resolution. > > This one is tricky. Maybe storing two reflog entries corresponding to > the unresolved stages? BTW, what happens if one tries to 'git stash' an unresolved index? So far this trash reflog and git stash have quite in common, and stashing an unresolved index certainly has value too. Nicolas