From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] First cut at libifying revlist generation
Date: Mon, 27 Feb 2006 10:00:09 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0602270947380.5937@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <7vpsl93395.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 26 Feb 2006, Junio C Hamano wrote:
> Johannes gets a test-pilot star for this. This also means we need a bit
> better set of tests.
Well, I don't deserve this. I cheated.
In my personal version of git, there are a few subtle things different
than in the official version. Most of them, I sent out already, and they
were rejected, such as
http://article.gmane.org/gmane.comp.version-control.git/10718, which
helped me tremendously in identyfing the bug.
But there is also a test case in my version, which was a failure,
originally. I wrote it to demonstrate that the stupid version of
git-fetch was stupid. It did not demonstrate that, but rather quite a bit
of (my) normal usage. That is the reason it takes a really long time for a
test case, and that in turn is the reason I did not dare to submit it.
Ciao,
Dscho
next prev parent reply other threads:[~2006-02-27 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 0:19 [PATCH] First cut at libifying revlist generation Linus Torvalds
2006-02-26 3:40 ` Junio C Hamano
2006-02-27 1:57 ` Johannes Schindelin
2006-02-27 3:05 ` Linus Torvalds
2006-02-27 3:11 ` Junio C Hamano
2006-02-27 3:19 ` Linus Torvalds
2006-02-27 5:09 ` Junio C Hamano
2006-02-27 5:20 ` Linus Torvalds
2006-02-27 16:54 ` Linus Torvalds
2006-02-27 23:55 ` Junio C Hamano
2006-02-27 9:00 ` Johannes Schindelin [this message]
2006-02-28 1:13 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0602270947380.5937@wbgn013.biozentrum.uni-wuerzburg.de \
--to=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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).