From: Johannes Sixt <j.sixt@viscovery.net>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Paul Richards <paul.richards@gmail.com>, git@vger.kernel.org
Subject: Re: Enumerating all objects in the Git object store
Date: Fri, 26 Mar 2010 21:11:47 +0100 [thread overview]
Message-ID: <201003262111.48298.j.sixt@viscovery.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1003261324350.694@xanadu.home>
On Freitag, 26. März 2010, Nicolas Pitre wrote:
> On Fri, 26 Mar 2010, Johannes Sixt wrote:
> > Use 'git rev-list --objects --all' to find all objects connected to all
> > refs (use something else than --all if you want to). Do *not* look at the
> > path that the tree and blob objects have attached - it is not authorative
> > information.
>
> Really??
Yes, really. Consider the same content at two differen paths. Now what?
rev-list will only ever list the object once.
-- Hannes
next prev parent reply other threads:[~2010-03-26 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:31 Enumerating all objects in the Git object store Paul Richards
2010-03-26 15:53 ` Johannes Sixt
2010-03-26 16:13 ` Jakub Narebski
2010-03-26 17:25 ` Nicolas Pitre
2010-03-26 20:11 ` Johannes Sixt [this message]
2010-03-26 20:24 ` Nicolas Pitre
2010-03-26 21:11 ` Paul Richards
2010-03-27 13:33 ` Michael J Gruber
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=201003262111.48298.j.sixt@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=paul.richards@gmail.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).