From: "Philippe Bruhat (BooK)" <philippe.bruhat@free.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Andrew Sayers" <andrew-git@pileofstuff.org>,
"Axel Bonnet" <axel.bonnet@ensimag.imag.fr>,
"Brian Downing" <bdowning@lavos.net>,
"Christian Couder" <chriscool@tuxfamily.org>,
"Clément Poulain" <clement.poulain@ensimag.imag.fr>,
"Eyvind Bernhardsen" <eyvind.bernhardsen@gmail.com>,
"Finn Arne Gangstad" <finnag@pvv.org>,
"Ian Ward Comfort" <icomfort@stanford.edu>,
"Jakub Narebski" <jnareb@gmail.com>, "Jeff King" <peff@peff.net>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Johan Herland" <johan@herland.net>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Michael J Gruber" <git@drmicha.warpmail.net>,
"Philippe Bruhat" <book@cpan.org>,
"Ramkumar Ramachandra" <artagnon@gmail.com>,
"Simo Melenius" <simo.melenius@i>
Subject: Re: What's cooking in git.git (Jun 2010, #02; Wed, 16)
Date: Thu, 17 Jun 2010 18:42:13 +0200 [thread overview]
Message-ID: <20100617164212.GG20658@swoosh> (raw)
In-Reply-To: <7vocf939vu.fsf@alter.siamese.dyndns.org>
On Thu, Jun 17, 2010 at 09:24:21AM -0700, Junio C Hamano wrote:
>
> > * ab/tap (2010-06-09) 4 commits
> > - We use TAP so the Perl test can run without scaffolding
> > - Skip tests in a way that makes sense under TAP
> > - Merge branch 'jc/t9129-any-utf8' into ab/tap
> > - Make test-lib.sh emit valid TAP format
> > (this branch uses jc/t9129-any-utf8.)
>
> I was not sure why TAP is worth the trouble, and I still am not sure.
Assuming I was on the list because I'm a Perl person, I'd say
that the benefit of TAP is that there are plenty of tools that
can parse it to provide nice reports.
> > * pb/maint-perl-errmsg-no-dir (2010-06-14) 1 commit
>
> There was a comment on what the proposed commmit log message said
> regarding $!; perhaps an update is in order?
Oh, that was for this, actually.
Ok, I'll send a new patch with the discussed change.
--
Philippe Bruhat (BooK)
Mankind is the story of the same mistakes in different places.
(Moral from Groo #1 (Image))
next prev parent reply other threads:[~2010-06-17 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 2:03 What's cooking in git.git (Jun 2010, #02; Wed, 16) Junio C Hamano
2010-06-17 11:35 ` Ævar Arnfjörð Bjarmason
2010-06-17 16:24 ` Junio C Hamano
2010-06-17 16:42 ` Philippe Bruhat (BooK) [this message]
2010-06-17 18:16 ` Ævar Arnfjörð Bjarmason
2010-06-17 19:05 ` Clément Poulain
2010-06-17 23:37 ` Junio C Hamano
2010-06-18 6:30 ` Matthieu Moy
2010-06-21 18:35 ` Zhang Le
2010-06-17 20:10 ` [PATCH v2] send-email: ask about and declare 8bit mails Thomas Rast
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=20100617164212.GG20658@swoosh \
--to=philippe.bruhat@free.fr \
--cc=Jens.Lehmann@web.de \
--cc=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=axel.bonnet@ensimag.imag.fr \
--cc=bdowning@lavos.net \
--cc=book@cpan.org \
--cc=chriscool@tuxfamily.org \
--cc=clement.poulain@ensimag.imag.fr \
--cc=eyvind.bernhardsen@gmail.com \
--cc=finnag@pvv.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=icomfort@stanford.edu \
--cc=jnareb@gmail.com \
--cc=johan@herland.net \
--cc=johannes.schindelin@gmx.de \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=simo.melenius@i \
--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).