git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conrad Irwin <conrad.irwin@gmail.com>
To: git@vger.kernel.org
Cc: conrad.irwin@gmail.com
Subject: [PATCH v2] git-commit --patch
Date: Wed,  2 Feb 2011 21:25:29 -0800	[thread overview]
Message-ID: <1296710732-12493-1-git-send-email-conrad.irwin@gmail.com> (raw)

This patch-set adds support for git-commit --patch, and tidies up some of the
rough edges of git commit --interactive.

The motivation is to support my current workflow, which goes something like:

1. Hack out the basic structure of the feature that I'm working on, until I have
   something that looks like it will work.
2. Split this into several commits with a more logical flow (i.e. some that add
   support for the techniques I want to use for the actual feature, then the
   feature itself).
3. Start fleshing out the implementation, and bug-fixing, with lots of
   git-commit --fixup so that the changes end up in the right commit.
4. At the end of the day, a big rebase -i to make the history readable.

This is just about doable with git-add -p, or git-commit --interactive, but
it's very inefficient. I take the presence of git commit --fixup to imply that
other people are doing similar, if less extreme things, so assume that they
would like a git-commit -p too.

Conrad

             reply	other threads:[~2011-02-03  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03  5:25 Conrad Irwin [this message]
2011-02-03  5:25 ` [PATCH 1/3] Use a temporary index for git commit --interactive Conrad Irwin
2011-02-03  5:25 ` [PATCH 2/3] Allow git commit --interactive with paths Conrad Irwin
2011-02-03  5:25 ` [PATCH 3/3] Add support for -p/--patch to git-commit Conrad Irwin
2011-02-06 21:06 ` [PATCH v2] git-commit --patch Conrad Irwin

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=1296710732-12493-1-git-send-email-conrad.irwin@gmail.com \
    --to=conrad.irwin@gmail.com \
    --cc=git@vger.kernel.org \
    /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).