git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Lord <lord@emf.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git <git@vger.kernel.org>
Subject: Re: arch 2.0 first source available (git related)
Date: Mon, 11 Jul 2005 14:36:56 -0700	[thread overview]
Message-ID: <1121117816.16511.5.camel@dev1.seyza.com> (raw)
In-Reply-To: <20050711193944.GA5981@pasky.ji.cz>

On Mon, 2005-07-11 at 21:39 +0200, Petr Baudis wrote:
> Dear diary, on Sat, Jul 09, 2005 at 04:20:13PM CEST, I got a letter
> where Thomas Lord <lord@emf.net> told me that...
> > The prereq graph is, indeed, an improvement.  
> ..snip..

> But object retrieval can be potentially as much as linear to the depth
> of the prereq graph, right? 

Potentially but not, by far, in the common case.

Moreover, that depth is an arbitrary parameter which user's can
freely vary -- that's part of the point.


> I don't think any of the benefits you listed
> are worth the complication, and you can still do the reachability
> analysis pretty easily. (And I think it takes the same number of
> roundtrips when downloading from remote server?)
> 

I don't agree that any complication is added.  I know that 
some complications are avoided with this approach.

-t

  reply	other threads:[~2005-07-11 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  0:12 arch 2.0 first source available (git related) Thomas Lord
2005-07-09 11:39 ` Petr Baudis
2005-07-09 14:20   ` Thomas Lord
2005-07-11 19:39     ` Petr Baudis
2005-07-11 21:36       ` Thomas Lord [this message]
2005-07-11 23:31         ` Petr Baudis
2005-07-12  0:05           ` Thomas Lord

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=1121117816.16511.5.camel@dev1.seyza.com \
    --to=lord@emf.net \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).