From: Clark Williams <clark.williams@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Odd problem in repository
Date: Tue, 24 Apr 2007 12:44:32 -0500 [thread overview]
Message-ID: <462E4200.7080206@gmail.com> (raw)
In-Reply-To: <20070424173048.GA5942@spearce.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Shawn O. Pearce wrote:
> Clark Williams <clark.williams@gmail.com> wrote:
>> 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
>
> This is a change in Git versions. Pre Git-1.5.0 we used to put all
> of the branches from the remote system into refs/heads, but now in
> 1.5.0 and later we put them in refs/remotes/origin.
>
> Nothing screwed up on the central repository, its just the
> new layout. refs/heads is reserved for *this* local repository,
> while refs/remotes/$name is reserved for the heads of $name remote
> repository.
>
Ah, so I'm not totally inept, just unable to read release notes. Sigh.
But, I'm still confused. After you clone the central repository, with
the new layout, why can't I 'mock checkout -f mock-0-6-branch'? Do I
need to further qualify it, or create a local branch from it?
Probably a better question is: what man-page/web-page/mail-thread should
I read to figure this out?
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGLkIAqA4JVb61b9cRAn8VAJ9Q7U4ZxP4Jc6OSyd1rcVufbBOO6wCfdDUn
Pmo7URBzl8PcCSRXu5BqYc0=
=yl7q
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-04-24 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 17:24 Odd problem in repository Clark Williams
2007-04-24 17:30 ` Shawn O. Pearce
2007-04-24 17:35 ` J. Bruce Fields
2007-04-24 17:44 ` Clark Williams [this message]
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=462E4200.7080206@gmail.com \
--to=clark.williams@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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