git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Martin Langhoff" <martin.langhoff@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] cvsimport - streamline temp index file creation and avoid creating empty tmpfiles
Date: Sat, 24 Jun 2006 04:28:57 -0700	[thread overview]
Message-ID: <7vr71ex05i.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90606240416n563288f5q99a5ac81723776c3@mail.gmail.com> (Martin Langhoff's message of "Sat, 24 Jun 2006 23:16:04 +1200")

"Martin Langhoff" <martin.langhoff@gmail.com> writes:

> Johannes, Junio,
>
> I've managed to repro the problem -- which was totally reproduceable,
> I was just testing the wrong version of the script. The problem was
> quite obvious: when running an incremental, the first head would not
> get the index created properly. Even worse, when forking a new branch,
> the index would be empty too.
>
> Fixed both cases and posted separately.

Thanks.  Will be in "next".

  reply	other threads:[~2006-06-24 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 16:14 CVS import broken? Johannes Schindelin
2006-06-24  5:09 ` [PATCH] cvsimport - streamline temp index file creation and avoid creating empty tmpfiles Martin Langhoff
2006-06-24  6:59   ` Junio C Hamano
2006-06-24  9:50   ` Johannes Schindelin
2006-06-24 10:05     ` Junio C Hamano
2006-06-24 11:16       ` Martin Langhoff
2006-06-24 11:28         ` Junio C Hamano [this message]
2006-06-24 19:05       ` Johannes Schindelin
2006-06-24 10:08     ` Martin Langhoff

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=7vr71ex05i.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    /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).