git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Database consistency after a successful pull

From
MJMcMullan, Jason <jason.mcmullan@timesys.com>
Date
Jun 6, 2005, 18:30 UTC
Message-ID
<1118082657.8970.42.camel@jmcmullan.timesys>
In-Reply-To
<Pine.LNX.4.21.0506061000531.30848-100000@iabervon.org>
On Mon, 2005-06-06 at 12:21 -0400, Daniel Barkalow wrote:
Show 6 quoted lines
> [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
Previous: Daniel Barkalow
Message 8 of 8 in “pull: gracefully recover from delta retrieval failure.”
  1. pull: gracefully recover from delta retrieval failure.Junio C Hamano, Jun 5, 2005
  2. Jason McMullanJun 5, 2005
  3. Daniel BarkalowJun 5, 2005
  4. Junio C HamanoJun 5, 2005
  5. Daniel BarkalowJun 5, 2005
  6. Database consistency after a successful pullMcMullan, Jason, Jun 6, 2005
  7. Daniel BarkalowJun 6, 2005
  8. McMullan, JasonJun 6, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.