From: "George Spelvin" <linux@horizon.com>
To: arjuncode@gmail.com
Cc: git@vger.kernel.org, linux@horizon.com
Subject: Re: Newbie question
Date: 23 Sep 2010 00:59:30 -0400 [thread overview]
Message-ID: <20100923045930.16223.qmail@science.horizon.com> (raw)
Jakub Narebski wrote:
> You have the repository itself (the object database containg all
> version info plus other info). Put those files and directories into
> <project>/.git subdirectory, and use "git checkout" from within it.
> You should have checked out files in <project>/ directory.
What he said. Cloning it in the first place is the easier approach, but
what happened is that you got a copy of a "bare" repostitory (without
checked-out files, suitable only for remote access), which is typically
in a directory named "project.git".
What you want is a normal tree, where all the git files are in "project/.git"
This is pretty easy to do:
mkdir project
mv project.git project/.git
cd project
git config core.bare true
git checkout
That does 3 things:
- Set up the directory structure correctly,
- unset the core.bare flag, which disables certain commands that
make no sense on a bare repository, and
- Check out a working copy
next reply other threads:[~2010-09-23 5:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 4:59 George Spelvin [this message]
2010-09-23 6:29 ` Newbie question Thomas Hochstein
-- strict thread matches above, loose matches on Subject: below --
2010-09-19 23:51 kinley
2010-09-19 23:59 ` Andrew Keller
2010-09-20 0:50 ` kinley
2010-09-20 1:47 ` Imran M Yousuf
2010-09-20 6:55 ` Kevin Ballard
2010-09-20 19:32 ` kinley
2010-09-20 8:31 ` Jakub Narebski
2010-09-20 8:39 ` Alex Riesen
2009-07-03 18:39 newbie question Alex K
2009-07-03 19:12 ` dloewenherz
2009-07-03 19:22 ` Junio C Hamano
2009-07-04 0:29 ` Sitaram Chamarty
2009-07-06 12:11 ` Michael J Gruber
2006-05-16 7:03 Li Yang-r58472
2006-05-16 7:09 ` Matthias Kestenholz
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=20100923045930.16223.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=arjuncode@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 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).