From: Mike Hommey <mh@glandium.org>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Question about your git habits
Date: Sat, 23 Feb 2008 15:08:20 +0100 [thread overview]
Message-ID: <20080223140820.GA4303@glandium.org> (raw)
In-Reply-To: <998d0e4a0802221847m431aa136xa217333b0517b962@mail.gmail.com>
On Sat, Feb 23, 2008 at 03:47:07AM +0100, J.C. Pizarro wrote:
> On 2008/2/23, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Fri, Feb 22, 2008 at 05:51:04PM -0800, Junio C Hamano wrote:
> > > Al Viro <viro@ZenIV.linux.org.uk> writes:
> > >
> > > > On Sat, Feb 23, 2008 at 02:37:00AM +0100, Jan Engelhardt wrote:
> > > >
> > > >> >do you tend to clone the entire repository repeatedly into a series
> > > >> >of separate working directories
> > > >>
> > > >> Too time consuming on consumer drives with projects the size of Linux.
> > > >
> > > > git clone -l -s
> > > >
> > > > is not particulary slow...
> > >
> > > How big is a checkout of a single revision of kernel these days,
> > > compared to a well-packed history since v2.6.12-rc2?
> > >
> > > The cost of writing out the work tree files isn't ignorable and
> > > probably more than writing out the repository data (which -s
> > > saves for you).
> >
> >
> > Depends... I'm using ext2 for that and noatime everywhere, so that might
> > change the picture, but IME it's fast enough... As for the size, it gets
> > to ~320Mb on disk, which is comparable to the pack size (~240-odd Mb).
>
>
> Yesterday, i had git cloned git://foo.com/bar.git ( 777 MiB )
> Today, i've git cloned git://foo.com/bar.git ( 779 MiB )
Why do you need to clone it again ? Just git fetch from it.
Mike
next prev parent reply other threads:[~2008-02-23 14:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 0:37 Question about your git habits Chase Venters
2008-02-23 1:26 ` Tommy Thorn
2008-02-23 1:28 ` Steven Walter
2008-02-23 1:37 ` Jan Engelhardt
2008-02-23 1:44 ` Al Viro
2008-02-23 1:51 ` Junio C Hamano
2008-02-23 2:09 ` Al Viro
[not found] ` <998d0e4a0802221823h3ba53097gf64fcc2ea826302b@mail.gmail.com>
2008-02-23 2:47 ` J.C. Pizarro
2008-02-23 11:39 ` Charles Bailey
2008-02-23 13:08 ` J.C. Pizarro
2008-02-23 13:17 ` Charles Bailey
2008-02-23 13:36 ` J.C. Pizarro
2008-02-23 14:01 ` Charles Bailey
2008-02-23 17:10 ` J.C. Pizarro
2008-02-23 18:16 ` Charles Bailey
2008-02-23 18:47 ` J.C. Pizarro
2008-02-23 19:28 ` Charles Bailey
2008-02-23 18:19 ` J.C. Pizarro
2008-02-23 14:08 ` Mike Hommey [this message]
2008-02-23 1:42 ` Junio C Hamano
2008-02-23 10:39 ` Samuel Tardieu
[not found] ` <998d0e4a0802221736q4e4c3a28l101522912f7d3caf@mail.gmail.com>
2008-02-23 2:46 ` J.C. Pizarro
2008-02-23 4:10 ` Daniel Barkalow
2008-02-23 5:03 ` Jeff Garzik
2008-02-23 9:18 ` Mike Hommey
2008-02-23 4:39 ` Rene Herman
2008-02-23 8:56 ` Willy Tarreau
2008-02-23 9:10 ` Sam Ravnborg
2008-02-23 13:07 ` Jakub Narebski
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=20080223140820.GA4303@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=jcpiza@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).