All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Make git-prune submodule aware (and fix a SEGFAULT in the process)
Date: Mon, 20 Aug 2007 09:39:50 +0100	[thread overview]
Message-ID: <200708200939.50955.andyparkins@gmail.com> (raw)
In-Reply-To: <7vtzqxen8b.fsf@gitster.siamese.dyndns.org>

On Saturday 2007 August 18, Junio C Hamano wrote:

> Andy, in the repository your fetch fails, if a fetch-pack
> without "--thin" before Linus's patch does not barf, that
> strongly suggests that the breakage you are seeing is related to
> this codepath.  And with Linus's patch, "fetch-pack --thin"
> would also be fixed.

I'm really sorry, somehow during my attempts to find the fault, the fault went 
away.  I think it's because I managed to get the fetch to work in some way, 
and from then on fetch completed perfectly.

The upshot of this is that I have no way to test this patch, until I manage to 
get myself in a similar state.  I'll wait until it happens again though and 
then try this patch.


Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  reply	other threads:[~2007-08-20  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 12:56 [PATCH] Make git-prune submodule aware (and fix a SEGFAULT in the process) Andy Parkins
2007-07-02 23:11 ` Junio C Hamano
2007-08-17  8:39 ` Andy Parkins
2007-08-17  9:14   ` Johannes Sixt
2007-08-17 16:56   ` Linus Torvalds
2007-08-17 23:48     ` Junio C Hamano
2007-08-20  8:39       ` Andy Parkins [this message]
2007-08-18  9:54     ` [PATCH] Make thin-pack generation subproject aware Junio C Hamano

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=200708200939.50955.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.