git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ping Yin <pkufranky@gmail.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git-add: introduce --edit (to edit the diff vs. the  index)
Date: Fri, 10 Apr 2009 20:59:34 +0200	[thread overview]
Message-ID: <fabb9a1e0904101159w7ab19247k81f4b67b8a91198f@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0904102009440.10279@pacific.mpi-cbg.de>

Heya,

On Fri, Apr 10, 2009 at 20:10, Johannes Schindelin
<Johannes.Schindelin@gmx.de> > As others have mentioned, there _is_ a
reason we have a working directory.
> Please understand this as a "I do not like the idea of editing the index
> directly at all".

I do not intend use it as a replacement of the working directory, but
mostly as a way to split up patches easier. Mainly to _remove_ lines
that I staged that I would like to be in a different patch in the
series (possibly after doing 'git reset --soft'). I always go through
my a longer patch series multiple times until I am satisfied with the
result, this addition would make that a lot easier.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-04-10 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1239225986u.git.johannes.schindelin@gmx.de>
2009-04-08 21:30 ` [PATCH] git-add: introduce --edit (to edit the diff vs. the index) Johannes Schindelin
2009-04-08 21:32   ` Sverre Rabbelier
2009-04-09  2:00   ` Ping Yin
2009-04-10  1:43     ` Ping Yin
2009-04-10  2:03       ` Ping Yin
2009-04-10 18:10       ` Johannes Schindelin
2009-04-10 18:59         ` Sverre Rabbelier [this message]
2009-04-13 16:19           ` Johannes Schindelin
2009-04-13 16:59             ` Sverre Rabbelier
2009-04-11  1:11         ` Ping Yin
2009-04-13 16:21           ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fabb9a1e0904101159w7ab19247k81f4b67b8a91198f@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pkufranky@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).