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

Re: Unexpected behavior in git-rev-list

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 22, 2005, 21:26 UTC
Message-ID
<Pine.LNX.4.58.0509221424390.2553@g5.osdl.org>
In-Reply-To
<Pine.LNX.4.63.0509221617300.23242@iabervon.org>
On Thu, 22 Sep 2005, Daniel Barkalow wrote:
Show 8 quoted lines
> >
> > It's not entirely trivial. The biggest bummer is that we'd have to fake
> > out the parent info (ie the "parent" would have to be the previous entry
> > that changes it, not the real one).
> 
> How about a program that made the fake thing real? That is, actually wrote 
> to the database the entire history with only those paths included, and 
> only commits that change those paths.

I think it would be a fine thing to do. If/once git-rev-list can do the "limit by filename" part, generating a new git history that uses that shouldn't be that hard.

And yes, it would be a way to generate a "subproject" automatically.
		Linus
Previous: Daniel Barkalow
Message 9 of 9 in “Unexpected behavior in git-rev-list”
  1. Peter EriksenSep 18, 2005
  2. Linus TorvaldsSep 18, 2005
  3. Peter EriksenSep 18, 2005
  4. Peter EriksenSep 21, 2005
  5. Linus TorvaldsSep 21, 2005
  6. Junio C HamanoSep 21, 2005
  7. Linus TorvaldsSep 21, 2005
  8. Daniel BarkalowSep 22, 2005
  9. Linus TorvaldsSep 22, 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.