9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kencc, inferno hg, v9fs is big?, porting
Date: Thu,  1 Oct 2009 11:25:04 -0700	[thread overview]
Message-ID: <3e1162e60910011125l38553459kb4337c35d5dfa0c2@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60910011123vb8afcealf951feb5cb9ddccf@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

On Thu, Oct 1, 2009 at 11:23 AM, David Leimbach <leimy2k@gmail.com> wrote:

>
>
> On Thu, Oct 1, 2009 at 11:19 AM, ron minnich <rminnich@gmail.com> wrote:
>
>> On Thu, Oct 1, 2009 at 6:23 AM, Sam Watkins <sam@nipl.net> wrote:
>>
>> > I tried to check out v9fs, but the compressed git repo without checkout
>> is over
>> > 300Mb.
>>
>> That's git for you. When you go to git it, you git ALL of it. Kind of
>> like deciding to download sources and getting the entire venti arena.
>>
>> ron
>>
>> Wouldn't Mercurial do the same?  Darcs (a haskell source control system)
> let's you get a subset of all the history, and if a patch refers to a really
> old revision you don't have, will go get that and its dependencies.  It's
> like a lazy-repository.  At least I think that's how it works, or that's how
> it's been explained to me.
> Is there a way to git a partial repository or hg a partial repository?
>
> Dave
>


"Darcs 2 replaces the concept of "partial" repositories with "lazy" ones.
There has always been a desire to allow "lightweight" checkouts that don't
include the complete repo history. The darcs 1 solution to this was
"partial" repositories that only checked out history up to a point. This
approach worked to some extent, but didn't play with well with darcs
commands that expected the whole history to be present. The new "lazy"
concept offers similar benefits, and will pull down older remote patches on
demand if some command needs them. Lazy repositories are a great comprise
between features and performance."

There we go.  So I guess you just need Darcs2.

Dave

[-- Attachment #2: Type: text/html, Size: 3113 bytes --]

  reply	other threads:[~2009-10-01 18:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  4:27 [9fans] corrections to /sys/src/cmd/8l/l.h lucio
2009-10-01 10:22 ` sqweek
2009-10-01 13:23   ` [9fans] kencc, inferno hg, v9fs is big?, porting Sam Watkins
2009-10-01 13:48     ` Abhishek Kulkarni
2009-10-01 17:09       ` C H Forsyth
2009-10-01 16:59         ` Russ Cox
2009-10-02  1:27           ` jrm8005
2009-10-01 18:19     ` ron minnich
2009-10-01 18:23       ` David Leimbach
2009-10-01 18:25         ` David Leimbach [this message]
2009-10-01 18:26       ` Eric Van Hensbergen
2009-10-01 18:34         ` Vinu Rajashekhar
2009-10-02  4:52     ` [9fans] inferno from hg does not build out of the box Sam Watkins
2009-10-02  8:44       ` roger peppe
2009-10-02 10:44         ` C H Forsyth
2009-10-02 15:03         ` David Leimbach
2009-10-02 17:03       ` Tim Newsham
2009-10-02 18:31         ` Charles Forsyth
2009-10-02 18:39           ` Eric Van Hensbergen
2009-10-02 21:07             ` Charles Forsyth
2009-10-03 15:12               ` Sam Watkins
     [not found] <<4ac55705.48c3f10a.1efe.038e@mx.google.com>
2009-10-02  1:29 ` [9fans] kencc, inferno hg, v9fs is big?, porting erik quanstrom

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=3e1162e60910011125l38553459kb4337c35d5dfa0c2@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    /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).