git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb@cuci.nl>
To: git@vger.kernel.org
Subject: Re: [PATCH] Check for circular references causing 'lost' nodes
Date: Sat, 26 Apr 2008 16:41:53 +0200	[thread overview]
Message-ID: <20080426144153.GA21197@cuci.nl> (raw)
In-Reply-To: <20080425234556.C271E545D@aristoteles.cuci.nl>

The most likely cause for circular references are bad entries in the
grafts file (like I did once); since basically noone tells you where you
went wrong, it can be a bit puzzling to find out that part of your tree
goes dark sometimes, depending on which tool/options you pick to walk the
commit-tree.
-- 
Sincerely,                                                          srb@cuci.nl
           Stephen R. van den Berg (AKA BuGless).
"God gave us a penis and a brain but not enough blood
 to use both at the same time." -- Robin Williams

      reply	other threads:[~2008-04-26 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  8:48 [PATCH] Check for circular references causing 'lost' nodes Stephen R. van den Berg
2008-04-26 14:41 ` Stephen R. van den Berg [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

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

  git send-email \
    --in-reply-to=20080426144153.GA21197@cuci.nl \
    --to=srb@cuci.nl \
    --cc=git@vger.kernel.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 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).