git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Ittay Dror" <ittay.dror@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git commit -p? --loop?
Date: Wed, 3 Sep 2008 16:01:46 +0200	[thread overview]
Message-ID: <bd6139dc0809030701y4a07c1a4secf08883235af9c0@mail.gmail.com> (raw)
In-Reply-To: <48BE4839.8080305@gmail.com>

On Wed, Sep 3, 2008 at 10:18, Ittay Dror <ittay.dror@gmail.com> wrote:
> I find that many times I make changes to some files that should be part of
> different commits. What I do then is run 'git add -p' and 'git commit'
> several times until I commit all hunks. Does it make sense to anyone to add
> -p option following a '-a' and '--loop' option (that will run until user
> requests to end or nothing to commit)?

I wonder if "git commit --interactive" would not suit your needs?

-- 
Cheers,

Sverre Rabbelier

      reply	other threads:[~2008-09-03 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03  8:18 git commit -p? --loop? Ittay Dror
2008-09-03 14:01 ` Sverre Rabbelier [this message]

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=bd6139dc0809030701y4a07c1a4secf08883235af9c0@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ittay.dror@gmail.com \
    --cc=sverre@rabbelier.nl \
    /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).