From: Pazu <pazu@pazu.com.br>
To: git@vger.kernel.org
Subject: git-commit: select which files to commit while editing the commit message
Date: Fri, 8 Dec 2006 12:36:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20061208T131919-178@post.gmane.org> (raw)
Junio's reworking of the git-commit documentation, and the ensuing discussion
about what is commited, and how do you select that, made me remember how much I
liked SVK -- particularly, how much I liked to remove files from the commit
message template, and have them removed from the commit.
At first, I thought "great opportunity to contribute my first patch to git",
until I realized that git-commit is written in bash, and my brain refuses to
understand that. Yep, I'm that bad. So I'm writing this, and maybe someone
well-versed in bash will find this a good idea and code it :-)
For those not familiar with SVK, if you remove the files mentioned in the commit
template (that "here are the files that you're about to commit" part), SVK won't
commit them. For example, if I modify a couple of files in git, and execute 'git
commit -a', an editor will popup showing something like this:
# Please enter the commit message for your changes.
# (Comment lines starting with '#' will not be included)
# On branch refs/heads/next
# Updated but not checked in:
# (will commit)
#
# modified: perl/Makefile
# modified: var.c
Here's where the magic would happen. Removing the line "modified: var.c" would
remove var.c from this commit. Of course, the template message should be
modified to tell the user he can do that.
So, what do you think about this?
-- Pazu
next reply other threads:[~2006-12-08 12:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 12:36 Pazu [this message]
2006-12-08 19:18 ` git-commit: select which files to commit while editing the commit message Junio C Hamano
2006-12-08 19:32 ` Jakub Narebski
2006-12-08 20:45 ` Luben Tuikov
2006-12-08 22:10 ` Josef Weidendorfer
2006-12-08 23:59 ` Seth Falcon
2006-12-09 0:07 ` Jakub Narebski
2006-12-09 0:37 ` Seth Falcon
2006-12-09 0:59 ` Junio C Hamano
2006-12-10 0:46 ` Josef Weidendorfer
2006-12-10 0:54 ` Junio C Hamano
2006-12-11 9:23 ` [PATCH] git-add --interactive (wip) Junio C Hamano
2006-12-11 10:47 ` Josef Weidendorfer
2006-12-12 21:51 ` Junio C Hamano
2006-12-12 22:15 ` Johannes Schindelin
2006-12-13 9:20 ` Andreas Ericsson
2006-12-13 3:15 ` Josef Weidendorfer
2006-12-13 5:34 ` Junio C Hamano
2006-12-13 10:42 ` Johannes Schindelin
2006-12-13 10:57 ` Shawn Pearce
2006-12-13 11:20 ` Johannes Schindelin
2006-12-13 20:31 ` Josef Weidendorfer
2006-12-09 7:02 ` git-commit: select which files to commit while editing the commit message Sean
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=loom.20061208T131919-178@post.gmane.org \
--to=pazu@pazu.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.