git commit workflow question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've been using git for a few months now and think I've mostly
gotten a handle on how it does things.  There's one workflow I'm
used to from ~10 years of using perforce that I miss when using git,
though:

With perforce I often have a bunch of files modified (having p4 add'd
or p4 edit'd them) and then only commit a subset of them.  I can do
this interactively by doing a p4 submit and just removing the files
I don't want to check in from the list in the changelist description
when I'm writing up the change description in $EDITOR, invoked by
p4 submit.

It seems like my options with git are to invoke git commit with
a specific list of things to commit, invoke git commit --interactive
and use the interactive menu thing to shuffle stuff around, or
manually unstage things until I have the index in a state where
a git commit without other arguments will do what I want.

Am I missing an obvious way to get a p4-like behavior where I can 
just remove the files from a list as part of preparing the commit in
my $EDITOR?  The above options I've found do get the job done but
I've found them to be a bit less convenient than what I'm used to.

Brian

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux