git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GIT 0.99.9

From
Linus Torvalds <torvalds@osdl.org>
Date
Oct 31, 2005, 02:52 UTC
Message-ID
<Pine.LNX.4.64.0510301838110.27915@g5.osdl.org>
In-Reply-To
<7vd5lnztav.fsf@assigned-by-dhcp.cox.net>
Btw, 
 one thing I'd like to see (maybe it already exists and I just have 
overlooked it) is some kind of simple readme or something about the 
different ways to limit the output of the various git commands.

I've several times been surprised to see people not realize that "git-whatchanged" takes a file list to limit the files it is interested in. I also suspect people don't realize that you can limit it by time and version and file list, all at the same time.

IOW, 
	git-whatchanged -p --pretty=short --since="2 weeks ago" v0.99.8..v0.99.9 Makefile

is a valid query: it basically asks for any change to the Makefile in between versions v0.99.8..v0.99.9, _and_ within the last two weeks, and asks to show it as a patch, with the shortened commit message.

Is it useful? The above exact line almost certainly isn't, but variations on the above definitely are. And I suspect a lot of people never even realized you could do something like that.

(The danger with date-based things is that something may be 4 months old, but it only got _merged_ yesterday, so it may be new to _you_. And the --since="2 weeks ago" will not show it, which can be surprising to people who expect things that are new to _them_ to be shown).

The above limiters now work with "git log" and "gitk" too (they've worked for a long time with "git-whatchanged", but only with the new git-rev-list functionality does the name-limiting work for the other commands).

It would be good to make this more well-known, because a lot of people probably end up using git not as developers, but just to follow what is going on. And then the different limiters are some of the most important parts (the date-one is likely the least important one, but limiting by version and name is _very_ important).

		Linus
Previous: H. Peter AnvinNext: Junio C Hamano
Message 18 of 26 in “GIT 0.99.9”
  1. Junio C HamanoOct 30, 2005
  2. A Large Angry SCMOct 30, 2005
  3. Junio C HamanoOct 30, 2005
  4. A Large Angry SCMOct 30, 2005
  5. Johannes SchindelinOct 30, 2005
  6. Linus TorvaldsOct 30, 2005
  7. rev-list --sparse?Junio C Hamano, Oct 30, 2005
  8. Linus TorvaldsOct 30, 2005
  9. Junio C HamanoOct 30, 2005
  10. Wolfgang DenkOct 30, 2005
  11. Junio C HamanoOct 30, 2005
  12. Wolfgang DenkOct 30, 2005
  13. Junio C HamanoOct 30, 2005
  14. Wolfgang DenkOct 30, 2005
  15. Ryan AndersonOct 30, 2005
  16. Junio C HamanoOct 30, 2005
  17. H. Peter AnvinOct 30, 2005
  18. Linus TorvaldsOct 31, 2005
  19. Junio C HamanoOct 31, 2005
  20. Linus TorvaldsOct 31, 2005
  21. Date-based limits (Was Re: GIT 0.99.9)Daniel Barkalow, Oct 31, 2005
  22. Junio C HamanoNov 1, 2005
  23. Daniel BarkalowNov 1, 2005
  24. rev-list: make --max- and --min-age a bit more usable.Junio C Hamano, Nov 2, 2005
  25. Linus TorvaldsNov 3, 2005
  26. Junio C HamanoNov 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.