From: Teemu Likonen <tlikonen@iki.fi>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jean-Luc Herren <jlh@gmx.ch>, Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: Cloning marks pack for .keep
Date: Tue, 8 Jul 2008 09:57:46 +0300 [thread overview]
Message-ID: <20080708065746.GA3536@mithlond.arda.local> (raw)
In-Reply-To: <20080708044606.GC2542@spearce.org>
Shawn O. Pearce wrote (2008-07-08 04:46 +0000):
> Jean-Luc Herren <jlh@gmx.ch> wrote:
> > After cloning a local repository with "git clone file://...", the
> > resulting repo had one big pack file, as expected, but also
> > a matching ".keep" file. Certainly this is a bug, isn't it? The
> > same happens if I clone git.git. I used git 1.5.6.1 but observed
> > the same with the current master. I bisected this behavior to
> > commit fa740529 by Shawn O. Pearce (CC'ing him). Since this dates
> > back to 2007, I wonder if maybe only I am seeing this, but I cannot
> > think of any reason for it.
>
> This is a known issue to me; I have been seeing this behavior myself
> since probably fa74 hit next. I just don't clone often so I've never
> thought about it much. ;-)
Earlier I noticed that this issue sometimes causes the repository to
grow pretty much after "git gc" because .keep packs are not touched.
This was discussed two months ago:
http://thread.gmane.org/gmane.comp.version-control.git/81856
I tend to think that .keep packs are not good idea at least for small
and medium sized repos. For _really_ big ones I'm not sure.
prev parent reply other threads:[~2008-07-08 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 21:27 Cloning marks pack for .keep Jean-Luc Herren
2008-07-08 4:46 ` Shawn O. Pearce
2008-07-08 6:57 ` Teemu Likonen [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=20080708065746.GA3536@mithlond.arda.local \
--to=tlikonen@iki.fi \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jlh@gmx.ch \
--cc=spearce@spearce.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).