From: Jakub Narebski <jnareb@gmail.com>
To: kinley <arjuncode@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Newbie question
Date: Mon, 20 Sep 2010 01:31:50 -0700 (PDT) [thread overview]
Message-ID: <m31v8pl11m.fsf@localhost.localdomain> (raw)
In-Reply-To: <1284940287810-5548737.post@n2.nabble.com>
kinley <arjuncode@gmail.com> writes:
> I am new to question. Please help me with this.
> I copied an already existing project from a remote server using scp to my
> local directory.
In the future use "git clone <scp-location>" instead of 'scp'.
> The contents of this directory are
> branches
> config
> description
> HEAD
> hooks
> info
> objects
> ref
>
> I checked all the directories and sub-directories but could not find a
> single source code file (in C language).
> All I can see at the leaf level appear to be MD5 hash code.
>
> Is there any command to retrieve the source files ?
> As per manual, only then I guess I can add them to git.
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.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-09-20 8:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 23:51 Newbie question 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 [this message]
2010-09-20 8:39 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 4:59 George Spelvin
2010-09-23 6:29 ` Thomas Hochstein
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=m31v8pl11m.fsf@localhost.localdomain \
--to=jnareb@gmail.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).