git/list[1] front-page[2] threads[3] people[4] search[5] about
 

getting started, happy with cmd line on windows [Scanned]

From
CRConor Rafferty <conor.rafferty@altmore.co.uk>
Date
Dec 26, 2008, 13:44 UTC
Message-ID
<BB5F02FD3789B54E8964D38D6775E718242D07@ALTMORE-SVR.altmore.local>

We want to use git to a) archive old versions of our project that have till now had no SCM applied b) moving forward, provide robust SCM on new versions of project

Just to get familiar, I created a folder, ran
$ git init

then created a few files: ABC.txt, AC.txt, BC.txt, C.txt This mimics our real life sitch for purpose (a), files are in version A, but not in version B, which introduces new files, whick might not be in version C

$ git add *c*.txt $ git commit -m "version A"

so now ABC.txt and AC.txt are in the repo, at a commit with comment "version A"

$ git show
confirms this
$ git status

confirms that BC.txt and C.txt have not been tracked - great, as designed

I then deleted all files from the working directory, so I can pull out ONLY the ones in version A. I tried both fetch and checkout - but nothing was copied into working dir How do I do this ?

NB along the way I also tagged this first commit as "tag_versionA" also tried

$ git checkout tag_versionA which changed HEAD back to version A, but didn't create the files

Seems like I'm missing some fundamental concepts here - from other SCM's, I understood fetch or checkout would copy files into your working dir that were replicas of the versions stored in repository

-- 
 
<http://www.altmore.co.uk/xNON_SITE/SignatureFiles/AltmoreIT_signature_l
ogo.JPG> 

Conor Rafferty BSc (Hons.)
REGIONAL MANAGER
Altmore IT Recruitment
Townsend Enterprise Park
28 Townsend Street
Belfast BT13 2ES 

T: +44 (0)28 9032 8400
E: conor.rafferty@altmore.co.uk
W: www.altmore.co.uk <http://www.altmore.co.uk/>  

LinkedIn: http://www.linkedin.com/in/conorrafferty

________________________________

This electronic message contains information from Altmore IT Recruitment
which may be privileged or confidential. The information is intended to
be for the use of the individual(s) or entity named above. If you are
not the intended recipient be aware that any disclosure, copying
distribution or use of the contents of this information is prohibited.
If you have received this electronic message in error, please notify us
by telephone or email (to the numbers or address above) immediately.
Next: René Scharfe
Message 1 of 7 in “getting started, happy with cmd line on windows [Scanned]”
  1. Conor RaffertyDec 26, 2008
  2. René ScharfeDec 26, 2008
  3. ZorbaDec 26, 2008
  4. Junio C HamanoDec 26, 2008
  5. ZorbaDec 27, 2008
  6. Daniel BarkalowDec 28, 2008
  7. ZorbaDec 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.