Re: [3/5] Add http-pull
- From
- Brad Roberts <braddr@puremagic.com>
- Date
- Apr 21, 2005, 03:27 UTC
- Message-ID
- <Pine.LNX.4.44.0504202026180.2625-100000@bellevue.puremagic.com>
- In-Reply-To
- <20050417195900.GH1461@pasky.ji.cz>
On Sun, 17 Apr 2005, Petr Baudis wrote:
Show 25 quoted lines
> Date: Sun, 17 Apr 2005 21:59:00 +0200 > From: Petr Baudis <pasky@ucw.cz> > To: Daniel Barkalow <barkalow@iabervon.org> > Cc: git@vger.kernel.org > Subject: Re: [3/5] Add http-pull > > Dear diary, on Sun, Apr 17, 2005 at 09:24:27PM CEST, I got a letter > where Daniel Barkalow <barkalow@iabervon.org> told me that... > > On Sun, 17 Apr 2005, Petr Baudis wrote: > > > > > Dear diary, on Sun, Apr 17, 2005 at 08:49:11PM CEST, I got a letter > > > where Daniel Barkalow <barkalow@iabervon.org> told me that... > > > > There's some trickiness for the history of commits thing for stopping at > > > > the point where you have everything, but also behaving appropriately if > > > > you try once, fail partway through, and then try again. It's on my queue > > > > of things to think about. > > > > > > Can't you just stop the recursion when you hit a commit you already > > > have? > > > > The problem is that, if you've fetched the final commit already, and then > > the server dies, and you try again later, you already have the last one, > > and so you think you've got everything. > > Hmm, some kind of journaling? ;-)
How about fetching in the inverse order. Ie, deepest parents up towards current. With that method the repository is always self consistent, even if not yet current.
Later, Brad