From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: ** X-Spam-ASN: AS31976 209.132.176.0/21 X-Spam-Status: No, score=2.6 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,HEADER_FROM_DIFFERENT_DOMAINS,INVALID_MSGID, MSGID_FROM_MTA_HEADER,MSGID_NOFQDN1,PLING_QUERY,RP_MATCHES_RCVD, UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 Received: (qmail 8157 invoked by uid 111); 24 Jun 2008 22:47:22 -0000 Received: from vger.kernel.org (HELO vger.kernel.org) (209.132.176.167) by peff.net (qpsmtpd/0.32) with ESMTP; Tue, 24 Jun 2008 18:47:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752827AbYFXWrM (ORCPT ); Tue, 24 Jun 2008 18:47:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751424AbYFXWrL (ORCPT ); Tue, 24 Jun 2008 18:47:11 -0400 Received: from w2.willowmail.com ([64.243.175.54]:60281 "HELO w2.willowmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751281AbYFXWrK (ORCPT ); Tue, 24 Jun 2008 18:47:10 -0400 Received: (qmail 21857 invoked by uid 90); 24 Jun 2008 22:47:03 -0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "David Jeske" To: Brandon Casey Cc: "Jakub Narebski" , "Boaz Harrosh" , git@vger.kernel.org Subject: Re: why is git destructive by default? (i suggest it not be!) X-Mailer: Willow v0.02 Date: Tue, 24 Jun 2008 22:13:13 -0000 Message-ID: Received: from 67.188.42.104 at Tue, 24 Jun 2008 22:13:13 -0000 References: In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org -- Brandon Casey wrote: > I only have the same advice I gave to Boaz. I think you should try to adjust > your workflow so that 'git reset' is not necessary. It seems that for the > functions you're trying to perform, 'checkout' and 'branch' should be used > rather than 'reset'. Even when I change my workflow to avoid 'reset', I believe that the user-interface of git will be stronger if it is a simpler expression of the same functionality. One way to simplify it is to use convention that is standardized across a set of tools so we don't have to learn every little nuance of every little feature independently. Two things I'd like to make it easy for users to never do are: - delete data - cause refs to be dangling Therefore, I'd like a simple convention I can apply across all commands, so that if users never do them, they'll never do either of the above things. I'm not alone. I think some of the impedance mismatch between my suggestions, and current usage, has to do with where I'd like to be next. This is a meaty topic, I'll start another thread on "policy and mechanism for less-connected clients". > I'm not sure why you want to use reset so often. If there is something in the > documentation that led you to want to use reset maybe it can be changed so that > other users are not led in the same way. Yes, it's a problem in the git-gui and the "reset --hard" documentation. I'm working on a patch.