From: Jonathan Nieder <jrnieder@gmail.com>
To: Soham Mehta <soham@box.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Intriguing error with Git 1.6.3.1: Too many open files
Date: Wed, 11 Jan 2012 01:18:51 -0600 [thread overview]
Message-ID: <20120111071851.GA28655@burratino> (raw)
In-Reply-To: <CALjyegVzchN==DEsARD65jEmz0BkkbYMQRhG=ujNiGCBHuB4SQ@mail.gmail.com>
Soham Mehta wrote:
> I haven't played with versions yet.
For almost all purposes, the latest stable version should work fine
(v1.7.8.3 at the moment). The people on this list tend to be very
keen to hear about cases where that's not true --- if people are stuck
using old versions because of regressions, that means we're failing.
> Are you alluding that #2 on this
> list may have addressed it?
> https://raw.github.com/gitster/git/master/Documentation/RelNotes/1.7.4.2.txt
Not exactly. I was thinking of commit c7934306 (Limit file
descriptors used by packs, 2011-02-28).
In git time, 1.6.3.1 is ancient history. There are many little fixes
and performance improvements you are missing out on.
Just my two cents,
Jonathan
prev parent reply other threads:[~2012-01-11 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 2:44 Intriguing error with Git 1.6.3.1: Too many open files Soham Mehta
2012-01-11 3:09 ` Jonathan Nieder
2012-01-11 6:52 ` Soham Mehta
2012-01-11 7:18 ` Jonathan Nieder [this message]
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=20120111071851.GA28655@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=soham@box.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).