All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: git@vger.kernel.org
Subject: Where'd my GIT tree go?
Date: Wed, 6 Jul 2005 20:23:11 -0700	[thread overview]
Message-ID: <12c511ca0507062023291a098e@mail.gmail.com> (raw)

http://www.kernel.org/git has stopped showing my linux-2.6 tree (the
"to Linus" one, my "test-2.6" tree is still there).

This is probably my fault ... but I'm not sure exactly why.

Here's what I did.  Last Thursday I applied a set of patches ... and my "apply"
script choked on one of them.  Some casual inspection convinced me that the
changes had been applied, and I pushed the tree up to kernel.org.

But I was wrong, the 2nd out od a series of six was all messed up.  And I'd
applied a couple more patches on top of that.  Since none of this had been
pulled by Linus, I thought I'd clean it up and apologise to anyone who had
pulled from my tree.

So I backed HEAD up to the last good commit.  Re-applied the changes with
a fixed version of the script, and then expected to find some detritus from
the first application in .git/objects.  But "git-fsck-cache --unreachable ..."
only complained about the 2.6.11 tag/tree.  Odd.

Then I pushed up to master.kernel.org ... and an hour later when the mirrors
did their thing, git-web stopped showing my tree.

HEAD is still a symlink to refs/heads/master.  And that has the SHA1 of my
most recent commit ... which is present in .git/objects.

So what's wrong???

-Tony

             reply	other threads:[~2005-07-07  3:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  3:23 Tony Luck [this message]
2005-07-07  3:59 ` Where'd my GIT tree go? Jon Seymour
2005-07-07  4:48   ` Tony Luck
2005-07-07 20:48     ` Thomas Gleixner

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=12c511ca0507062023291a098e@mail.gmail.com \
    --to=tony.luck@gmail.com \
    --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 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.