git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Junio C Hamano" <junkio@cox.net>,
	"Linus Torvalds" <torvalds@osdl.org>,
	"GIT Mailling list" <git@vger.kernel.org>
Subject: Re: Database consistency after a successful pull
Date: Mon, 06 Jun 2005 14:30:56 -0400
Date: Mon, 6 Jun 2005 14:23:57 -0400	[thread overview]
Message-ID: <1118082657.8970.42.camel@jmcmullan.timesys> (raw)
In-Reply-To: <Pine.LNX.4.21.0506061000531.30848-100000@iabervon.org>

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

On Mon, 2005-06-06 at 12:21 -0400, Daniel Barkalow wrote:
> [snip snip]
>
> My bias is to call a database consistent with only deltas having the
> referents; the rest goes towards completeness, since you have and can read
> everything that you have anything for (but may not be able to do some
> particular operation).

Now, if we had consistent URIs for the .git/branches/* files, we could
do 'lazy-pull' and really have our cake and eat it too.

-- 
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-06-06 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05  6:11 [PATCH] pull: gracefully recover from delta retrieval failure Junio C Hamano
2005-06-05 16:38 ` Jason McMullan
2005-06-05 17:24   ` Daniel Barkalow
2005-06-05 17:46   ` Junio C Hamano
2005-06-05 20:02     ` Daniel Barkalow
2005-06-06 13:50       ` Database consistency after a successful pull McMullan, Jason
2005-06-06 16:21         ` Daniel Barkalow
2005-06-06 18:30           ` McMullan, Jason [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1118082657.8970.42.camel@jmcmullan.timesys \
    --to=jason.mcmullan@timesys.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).