From: "Alexey Dobriyan" <adobriyan@gmail.com>
To: git@vger.kernel.org
Subject: selective git-update-index per diff(1) chunks
Date: Fri, 1 Dec 2006 14:23:14 +0300 [thread overview]
Message-ID: <b6fcc0a0612010323x7554e47m5e6bdafe85fc8224@mail.gmail.com> (raw)
Pretty often I end up with a file with two simple orthogonal fixes in it.
git-diff shows me both, that's OK.
Now I want to commit them as two separate commits. So far, it's
* getting full diff
* cp(1)
* hand-edit both diffs
* commit first
* commit second
Has anyone thought about aggregating this into git-update-index or
somewhere?
git-update-index -C1,3 #chunks 1, 3
git commit
git-update-index -C1,3 # chunks 2,5 in original numbering
git commit
next reply other threads:[~2006-12-01 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 11:23 Alexey Dobriyan [this message]
2006-12-01 11:33 ` selective git-update-index per diff(1) chunks Peter Baumann
2006-12-01 11:38 ` Junio C Hamano
2006-12-01 16:45 ` Anand Kumria
2006-12-01 19:42 ` Johannes Schindelin
2006-12-02 21:08 ` Sam Vilain
2006-12-01 16:06 ` Linus Torvalds
2006-12-04 17:33 ` Sven Verdoolaege
2006-12-04 18:05 ` Jakub Narebski
[not found] ` <20061204202102.GH940MdfPADPa@greensroom.kotnet.org>
2006-12-04 20:46 ` Jakub Narebski
2006-12-04 21:51 ` Sven Verdoolaege
2006-12-04 22:35 ` Jakub Narebski
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=b6fcc0a0612010323x7554e47m5e6bdafe85fc8224@mail.gmail.com \
--to=adobriyan@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).