From: Pascal Obry <pascal@obry.net>
To: Jeff King <peff@peff.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: git-reflog infinite loop
Date: Wed, 11 Jun 2008 07:46:13 +0200 [thread overview]
Message-ID: <484F66A5.6070205@obry.net> (raw)
In-Reply-To: <20080611034718.GB7198@sigill.intra.peff.net>
Jeff King a écrit :
> I can't reproduce here, so presumably it is some condition in your
> repository;
Yes, I have this problem on a single repository and no problem on the
others (~10).
> can you make a tarball of your .git directory available?
No I can't :(
Is there some git-reflog options I can try to help finding this problem?
Thanks,
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2008-06-11 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:44 git-reflog infinite loop Pascal Obry
2008-06-11 3:47 ` Jeff King
2008-06-11 5:46 ` Pascal Obry [this message]
2008-06-11 7:03 ` Jeff King
2008-06-11 18:58 ` Pascal Obry
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=484F66A5.6070205@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).