From: "Zorba" <cr@altmore.co.uk>
To: git@vger.kernel.org
Subject: Re: for newbs = little exercise / tutorial / warmup for windows and other non-sophisticated new Git users :-)
Date: Tue, 30 Dec 2008 21:39:41 -0000 [thread overview]
Message-ID: <gje4ff$ip6$4@ger.gmane.org> (raw)
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...
>> 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. :-)
next prev parent reply other threads:[~2008-12-30 21:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 21:56 for newbs = little exercise / tutorial / warmup for windows and other non-sophisticated new Git users :-) Zorba
2008-12-28 1:29 ` Zorba
2008-12-29 23:05 ` Jeff Whiteside
2008-12-30 4:24 ` Zorba
2008-12-30 5:33 ` Jeff Whiteside
2008-12-30 12:19 ` Zorba
2008-12-30 5:34 ` Sitaram Chamarty
2008-12-30 16:07 ` Zorba
2008-12-30 17:22 ` Zorba
2008-12-30 17:44 ` Zorba
2008-12-30 18:35 ` Jeff Whiteside
2008-12-30 21:39 ` Zorba [this message]
2008-12-30 22:03 ` Jeff Whiteside
2008-12-30 23:29 ` Daniel Barkalow
2008-12-31 0:31 ` Zorba
2008-12-30 21:27 ` Zorba
2008-12-30 21:49 ` Boyd Stephen Smith Jr.
2008-12-30 22:17 ` Boyd Stephen Smith Jr.
2008-12-30 22:39 ` Boyd Stephen Smith Jr.
2008-12-31 1:43 ` Sitaram Chamarty
2008-12-30 19:42 ` Daniel Barkalow
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='gje4ff$ip6$4@ger.gmane.org' \
--to=cr@altmore.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.