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

Re: for newbs = little exercise / tutorial / warmup for windows and other non-sophisticated new Git users :-)

From
ZZorba <cr@altmore.co.uk>
Date
Dec 30, 2008, 21:04 UTC
Message-ID
<gje4ff$ip6$4@ger.gmane.org>
In-Reply-To
<3ab397d0812301035w3dcd872fkae9509629a0ed7de@mail.gmail.com>
Thnks for reviewing !

"Jeff Whiteside" <jeff.m.whiteside@gmail.com> wrote in message news:3ab397d0812301035w3dcd872fkae9509629a0ed7de@mail.gmail.com...

Show 8 quoted lines
>> commit -a detects that files have been deleted, and takes them out of the 
>> index !
>> could also have used $ git rm <specific files> and then $ git commit ..
>
> hey! i like your changes! the post is pretty polished now.  the only
> thing else i would change (srysry), is the above.  "-a detects that
> files have been deleted"  -> heh, not true.  you don't need -a here;
> it does something else.

** haven't had time to review this but from what you say it looks like I forgot to take this out

> okay i just recreated your repo and did the same thing.  with your
> syntax "git checkout versionA ." i got the same result, and i'm not
> sure why, but i think it was because of the detached head.

** at Yves' (demerphq) request I reproduced and posted the exact sequence of commands this was from a reboot, going straight into git bash and running the warmup with NO git-resets at all

> good news, use "git checkout versionA", not "git checkout versionA ."
> (so, use it wihtout the dot), and you should be back in working order.

** yes but I don't get the files copied out into the tree which is all my little heart ever desired

> the other (good?)  news is that you probably _do_ want to be using git
> reset --hard in your case, because you're trying to build up a history
> from some project, so you do want to erase some faulty commits after
> you bodge something or miss some files.
** yes, now I know that git-reset is only for destruction, not navigation
> the bad news is that my opinion is that you should probably move on
> with your life, because my own past tells me that you'll never
> actually use those old project versions, hahah :p

** LOL, I have to admit I am enjoying this though, even if its driving me slightly potty - haha I didn't write these early versions so I just wanna have them around to rollback to if I end up hacking the thing to bits. But you're right - chances of using are slim - but you could say that about every version sitting in any given SCM repo. Thats why we have SCM, and why we insure our cars etc etc. :-)

Previous: Jeff WhitesideNext: Jeff Whiteside
Message 12 of 21 in “for newbs = little exercise / tutorial / warmup for windows and other non-sophisticated new Git users :-)”
  1. ZorbaDec 27, 2008
  2. ZorbaDec 28, 2008
  3. Jeff WhitesideDec 29, 2008
  4. ZorbaDec 30, 2008
  5. Jeff WhitesideDec 30, 2008
  6. ZorbaDec 30, 2008
  7. Sitaram ChamartyDec 30, 2008
  8. ZorbaDec 30, 2008
  9. ZorbaDec 30, 2008
  10. ZorbaDec 30, 2008
  11. Jeff WhitesideDec 30, 2008
  12. ZorbaDec 30, 2008
  13. Jeff WhitesideDec 30, 2008
  14. Daniel BarkalowDec 30, 2008
  15. ZorbaDec 31, 2008
  16. ZorbaDec 30, 2008
  17. Boyd Stephen Smith Jr.Dec 30, 2008
  18. Boyd Stephen Smith Jr.Dec 30, 2008
  19. Boyd Stephen Smith Jr.Dec 30, 2008
  20. Sitaram ChamartyDec 31, 2008
  21. Daniel BarkalowDec 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.