From: Clark Williams <clark.williams@gmail.com>
To: git@vger.kernel.org
Subject: Odd problem in repository
Date: Tue, 24 Apr 2007 12:24:02 -0500 [thread overview]
Message-ID: <462E3D32.60804@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello git-list,
We're experimenting with using git for the mock source repository on
fedoraproject.org. The CVS repository was converted over and I
successfully cloned a repository and went merrily on my way.
One of my collaborators cloned the repository the other day and found
that it didn't have any branches in it. I cloned a temp copy of it and
found that the files that normally would be in refs/heads to identify
the branches had somehow been moved to the directory
refs/remotes/origin. In my local repository (which was cloned
immediately after the CVS import), if I list what's in refs/heads, I get
this:
$ ls -F refs/heads
master mock mock-0-6-branch mock-0.7 origin
on the whacky cloned copy, I get this:
$ ls -F refs/heads
master
and if I look in refs/remotes/origin:
$ ls -F refs/remotes/origin
HEAD master mock mock-0-6-branch mock-0.7 origin
Can anyone come up with a way that I could have mangled the repository
with a push? I mean, I have no idea how that remotes/origin directory
got created; I don't even have an interactive login on
git.fedoraproject.org.
If anyone wants to see the repository, you can clone it from:
git://git.fedoraprojects.org/git/hosted/mock
I'm not sure if it makes sense to try and repair this or just start
anew. Any advice would be appreciated.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD4DBQFGLj0xqA4JVb61b9cRAhWYAJ49SDX6EnRxkFkJGjq5TUjhHjP2kwCWOJfK
obOqRJwU0vOq/aZDsM3glw==
=XwQr
-----END PGP SIGNATURE-----
next reply other threads:[~2007-04-24 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 17:24 Clark Williams [this message]
2007-04-24 17:30 ` Odd problem in repository Shawn O. Pearce
2007-04-24 17:35 ` J. Bruce Fields
2007-04-24 17:44 ` Clark Williams
2007-04-24 17:48 ` Shawn O. Pearce
2007-04-24 17:53 ` Clark Williams
2007-04-24 17:43 ` Jeffrey C. Ollie
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=462E3D32.60804@gmail.com \
--to=clark.williams@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.