From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] tar archive frontend for fast-import.
Date: Thu, 8 Feb 2007 16:01:41 -0500 [thread overview]
Message-ID: <20070208210141.GA1047@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0702082155210.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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.
prev parent reply other threads:[~2007-02-08 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 20:38 [PATCH 2/2] tar archive frontend for fast-import Shawn O. Pearce
2007-02-08 20:56 ` Johannes Schindelin
2007-02-08 21:01 ` Shawn O. Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070208210141.GA1047@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).