On Tue, 24 Jul 2007, Patrick Doyle wrote:
> ... and I don't commit until I've completed
> the particular feature I'm working on, I can get a fairly good idea of
> where I am and what I was doing last (which might be 5-7 days ago,
> given high priority interrupts on other projects, summer vacations,
> etc...) just by running a "git status". I see that there are 7 new
> files, and 2 modified files. I know that, when I fork my branch, I
> can use "git diff master" to see what's different between my branch
> and the master, but then I get the diff of all of the changes as well,
> which is too much information. "git diff --name-only" and "git diff
> --summary" are closer, but I can't tell what's been added vs. what's
> been changed. Any suggestions?
"git log -p ..master", or even simpler "gitk ..master"
I was hoping for something less verbose than a diff or a patch file --
something that just listed what has changed -- I'll have to
investigate whether your "my_status()" macro provides the information
for which I was looking -- thanks for the pointer.
"git log --stat ..master" perhaps?
--
Julian
---
The future isn't what it used to be. (It never was.)
-
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
