From: "David Frech" <david@nimblemachines.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: test suite fails if sh != bash || tar != GNU tar
Date: Tue, 10 Jul 2007 21:08:30 -0700 [thread overview]
Message-ID: <7154c5c60707102108g59280301pa5c3c0dc3911753d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707102020020.3412@woody.linux-foundation.org>
On 7/10/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, 11 Jul 2007, Johannes Schindelin wrote:
> > As for GNU tar, I think that this is easily fixable if you have access to
> > non-GNU tar. We do not use tar _ever_, except for the test suite, to
> > verify that things are working as expected.
> >
> > If you could put in some time to make the tests work, that would be
> > awesome.
>
> Yeah, it would be a good thing to get rid of any bashisms, but to _keep_
> it working somebody would then need to test every once in a while that it
> still works ;)
I'll see what I can do. As I'm planning on running git on both FreeBSD
and DragonFly for the forseeable future, and plan to track git's
evolution (running stable releases if not more bleeding-edge code), I
can run the test suite every time I build a new git.
Cheers,
- David
>
> Linus
>
--
If I have not seen farther, it is because I have stood in the
footsteps of giants.
next prev parent reply other threads:[~2007-07-11 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 2:39 test suite fails if sh != bash || tar != GNU tar David Frech
2007-07-11 2:49 ` Johannes Schindelin
2007-07-11 3:22 ` Linus Torvalds
2007-07-11 4:08 ` David Frech [this message]
2007-07-11 11:09 ` Johannes Schindelin
2007-07-11 21:26 ` Junio C Hamano
2007-07-11 21:33 ` David Frech
2007-07-11 21:43 ` Junio C Hamano
2007-07-11 21:57 ` David Frech
2007-07-11 21:56 ` 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=7154c5c60707102108g59280301pa5c3c0dc3911753d@mail.gmail.com \
--to=david@nimblemachines.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).