From: Theodore Ts'o <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.1.0
Date: Fri, 15 Aug 2014 19:18:22 -0400 [thread overview]
Message-ID: <20140815231822.GM10808@thunk.org> (raw)
In-Reply-To: <xmqqd2c1z7zu.fsf@gitster.dls.corp.google.com>
On Fri, Aug 15, 2014 at 03:46:29PM -0700, Junio C Hamano wrote:
> The latest feature release Git v2.1.0 is now available at the
> usual places.
I pulled down git v2.1.0, and when I tried to build it via:
make prefix=/usr/local profile-fast
The build died with this:
cannot open test-results/p5302-pack-index.subtests: No such file or directory at ./aggregate.perl line 77.
Makefile:7: recipe for target 'perf' failed
make[2]: *** [perf] Error 2
make[2]: Leaving directory '/usr/projects/git/git/t/perf'
Not a big deal, but I thought I would mention it.
Cheers,
- Ted
next prev parent reply other threads:[~2014-08-15 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 22:46 [ANNOUNCE] Git v2.1.0 Junio C Hamano
2014-08-15 23:18 ` Theodore Ts'o [this message]
2014-08-17 19:19 ` Junio C Hamano
2014-08-17 14:10 ` Ramsay Jones
2014-08-17 19:25 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140815231822.GM10808@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).