From: Paul Jakma <paul@clubi.ie>
To: git list <git@vger.kernel.org>
Subject: seperate commits for objects already updated in index?
Date: Tue, 14 Mar 2006 16:37:40 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0603141634010.5276@sheen.jakma.org> (raw)
Hi,
Dumb question, imagine you made changes to a few files, and ran
update-index at various stages in between:
$ git status
#
# Updated but not checked in:
# (will commit)
#
# modified: foo/ChangeLog
# modified: foo/whatever
# modified: bar/ChangeLog
# modified: bar/other
The changes in bar/ are unrelated to the changes in foo/ - how do you
commit each seperately? Git doesn't seem to want to let me:
$ git commit -o bar
Different in index and the last commit:
M bar/ChangeLog
M bar/other
You might have meant to say 'git commit -i paths...', perhaps?
git commit on its own wants to commit all the above files.
what's the silly thing I've missed?
Thanks.
regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
Fortune:
Never tell a lie unless it is absolutely convenient.
next reply other threads:[~2006-03-14 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 16:37 Paul Jakma [this message]
2006-03-14 17:00 ` seperate commits for objects already updated in index? Linus Torvalds
2006-03-14 17:04 ` Paul Jakma
2006-03-14 17:20 ` Linus Torvalds
2006-03-14 17:27 ` Paul Jakma
2006-03-14 23:51 ` Junio C Hamano
2006-03-15 3:24 ` Junio C Hamano
2006-03-15 13:28 ` Paul Jakma
2006-03-15 14:00 ` Andreas Ericsson
2006-03-15 19:25 ` Junio C Hamano
2006-03-15 19:43 ` Andreas Ericsson
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=Pine.LNX.4.64.0603141634010.5276@sheen.jakma.org \
--to=paul@clubi.ie \
--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).