From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Yuri Khan Newsgroups: gmane.emacs.devel Subject: Re: VC mode and git Date: Thu, 26 Mar 2015 01:30:49 +0600 Message-ID: References: <86sicte9j3.fsf@example.com> <83y4mlnee2.fsf@gnu.org> <20150325181959.GC3833@acm.fritz.box> <20150325192349.GE3833@acm.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1427311881 4108 80.91.229.3 (25 Mar 2015 19:31:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 25 Mar 2015 19:31:21 +0000 (UTC) Cc: Eli Zaretskii , Stefan Monnier , Emacs developers To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 25 20:31:20 2015 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 1Yar1J-000750-BU for ged-emacs-devel@m.gmane.org; Wed, 25 Mar 2015 20:31:17 +0100 Original-Received: from localhost ([::1]:41098 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yar1I-0005iN-PX for ged-emacs-devel@m.gmane.org; Wed, 25 Mar 2015 15:31:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60072) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yar1F-0005i6-6G for emacs-devel@gnu.org; Wed, 25 Mar 2015 15:31:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yar1D-0002dK-R5 for emacs-devel@gnu.org; Wed, 25 Mar 2015 15:31:13 -0400 Original-Received: from mail-ig0-x232.google.com ([2607:f8b0:4001:c05::232]:37399) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yar1C-0002ch-Kq; Wed, 25 Mar 2015 15:31:10 -0400 Original-Received: by igcxg11 with SMTP id xg11so35052703igc.0; Wed, 25 Mar 2015 12:31:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=klsmjz8YSY9ISs7ukrSAO80NxtUK6++rwGwvJDY4kN0=; b=z/Afh/Mfq4E9HoW6IMxSWuLz8BP/OIVCJFngWCZWNbilFXgoj4R8HvbLE2kYFK1LLk ZRfqRSJt5O65fw+gedfdEHyZ2ICF29Mq1Ib/r0zM8pTMHZX43J5zPhVkaa6D//EQZqNN RaJA9i4BofhcFU4myOHqEKs7+034uyu233Y+1ywUqpFmW3WZo8y6mFCwB0bwZBu2uzo4 Dh3LZi0JjKdq1ZXbt3FYUXO9sFbh3bOppoOzUmiAeOe7ofBE49Hd6uX7+O9nMTNo4uLh 7atb1dMPzQ4IxZZiClnb1AgDzaHoSb+nvg667pqGCIt3kQlviliCGtnKFYOwVp2eYsFz ztFw== X-Received: by 10.50.29.109 with SMTP id j13mr31986917igh.2.1427311870199; Wed, 25 Mar 2015 12:31:10 -0700 (PDT) Original-Received: by 10.107.3.132 with HTTP; Wed, 25 Mar 2015 12:30:49 -0700 (PDT) In-Reply-To: <20150325192349.GE3833@acm.fritz.box> X-Google-Sender-Auth: t92_gRI6J10ofg2BhT3Qzb_aJUk X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c05::232 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:184262 Archived-At: On Thu, Mar 26, 2015 at 1:23 AM, Alan Mackenzie wrote: >> [=E2=80=A6] with the index, I can do all of these things as soon as I >> feel the need. Then I call up the Magit status buffer which shows me >> all unstaged changes. I go over them and stage only those that I want >> to put in a single commit, e.g. all the spelling fixes. I make a >> commit, then repeat with the reduced set of changes. With a single >> key, I can stage all changes, or all changes to a single file, or an >> individual hunk, or a selected region. > > Isn't this what branches are meant to be for? Yes, the final result that I want is a set of unrelated series of commits. The difference is how I arrive at that result. Traditionally, one creates a branch, makes those and only those modifications that are meant for that branch, commits, repeats until ready. Branch switching in Git is lightweight. But doing all modifications in a single working copy avoids even that. Of course, it only scales up to a certain extent. Too many unrelated modifications become difficult to separate.