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

Re: [PATCH 2/2] tar archive frontend for fast-import.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 8, 2007, 21:01 UTC
Message-ID
<20070208210141.GA1047@spearce.org>
In-Reply-To
<Pine.LNX.4.63.0702082155210.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 7 quoted lines
> On Thu, 8 Feb 2007, Shawn O. Pearce wrote:
> 
> > Each tar is treated as one commit, with the commit timestamp coming
> > from the oldest file modification date found within the tar.
> 
> You mean the youngest, i.e. the newest file, right? (I did not read the 
> code yet...)

Arrggh! Yes, of course, the youngest/newest file. The code (and you) is right, the commit message is wrong. ;-)

-- 
Shawn.
Previous: Johannes Schindelin
Message 3 of 3 in “tar archive frontend for fast-import.”
  1. 2/2 tar archive frontend for fast-import.Shawn O. Pearce, Feb 8, 2007
  2. Johannes SchindelinFeb 8, 2007
  3. Shawn O. PearceFeb 8, 2007

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.