From: Tomas Carnecky <tom@dbservice.com>
To: Jeff King <peff@peff.net>
Cc: Robert Garrigos <robert@garrigos.cat>, git@vger.kernel.org
Subject: Re: unable to get type of object
Date: Wed, 01 Jun 2011 20:18:07 +0200 [thread overview]
Message-ID: <4DE6825F.9040608@dbservice.com> (raw)
In-Reply-To: <20110601160447.GA7132@sigill.intra.peff.net>
On 6/1/11 6:04 PM, Jeff King wrote:
> On Wed, Jun 01, 2011 at 09:11:07AM +0200, Robert Garrigos wrote:
>> Besides that I'm running git 1.2.4 and that the git command for that
>> version is fsck-objects, I'm not having any result at all.
> Wow, that's pretty ancient by git standards.
When looking through the last git survey I was wondering why there were
people still using pre 1.3.x versions. Here we finally meet one of them :)
v1.2.4 was released March 1, 2006. It has about 48k lines of code, while
master today has ~287k (counted using sloccount).
tom
prev parent reply other threads:[~2011-06-01 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 7:11 unable to get type of object Robert Garrigos
2011-06-01 9:39 ` Jakub Narebski
2011-06-01 10:05 ` Robert Garrigos
2011-06-01 16:04 ` Jeff King
2011-06-01 18:18 ` Tomas Carnecky [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=4DE6825F.9040608@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=robert@garrigos.cat \
/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).