From: Junio C Hamano <junkio@cox.net>
To: Dennis Stosberg <dennis@stosberg.net>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: t5501-old-fetch-and-upload.sh fails with NO_PYTHON=1
Date: Tue, 11 Apr 2006 11:06:54 -0700 [thread overview]
Message-ID: <7vlkuc56m9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060411170508.G14ba7e47@leonov.stosberg.net> (Dennis Stosberg's message of "Tue, 11 Apr 2006 19:05:08 +0200")
Dennis Stosberg <dennis@stosberg.net> writes:
> I have attached a simple fix, but is this test still useful at all?
Thanks. I am inclined to say that when we need the "make sure
this updated send-pack works with older receive-pack and vice
versa" tests the next time, the framework to call the
counterpart program from different vintage might be reusable but
what the test tries to test would be different, so keeping this
particular test would be somewhat useful as reference and
perhaps a starting point for such new test, but otherwise not
very much. And for that kind of usage, "the Net never forgets".
I'd vote for its removal. Thoughts?
next prev parent reply other threads:[~2006-04-11 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 17:05 t5501-old-fetch-and-upload.sh fails with NO_PYTHON=1 Dennis Stosberg
2006-04-11 18:06 ` Junio C Hamano [this message]
2006-04-11 21:31 ` Johannes Schindelin
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=7vlkuc56m9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=dennis@stosberg.net \
--cc=git@vger.kernel.org \
/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