Re: for newbs = little exercise / tutorial / warmup for windows and other non-sophisticated new Git users :-)
- From
- Jeff Whiteside <jeff.m.whiteside@gmail.com>
- Date
- Dec 29, 2008, 23:05 UTC
- Message-ID
- <3ab397d0812291505v77824e6fvdecebc80f38a5f89@mail.gmail.com>
- In-Reply-To
- <gj6kqq$nvh$4@ger.gmane.org>
hi zorb,
you have done a great justice here to inadvertently explaining the learning curve of git, through a few mistakes, especially for ppl behind in their scm use. i enjoyed reading your blog posts though, as they remind me of myself, not long ago.
you have a couple of mistakes i think you should correct.
-"Imagine a project with 4 versions, made up of various configurations of the three files." this line implies that you have branches (the word configurations). you should be focusing, at first, on a project that has a set number of files, and the content merely changes. ideally, you don't often add and rm files across versions. also, the project doesn't really have 4 versions, like windows has 4 different versions of vista, the project has 3 old versions and 1 new version.
"Setup a git index in the project directory" -this implies you're talking about the index. you're not. you're talking about the repository. either make it clear that the index is an intermediary staging area, or ignore its existence and change all git-add && git-commit references to git-commit -a references. this will ease the user of older scms into git.
-"Rollback to each of the versions, starting with version A" this is bad. you're saying rollback. to others that have used scms, this will mean, "retrieve an older copy", but in git, this is DELETING all the versions after the version that you "rollback" to. your blog post shouldn't discuss the git-reset --hard command at all, since you're rewriting history, which is dangerous. afaik, most scms don't allow you to rewrite history. to "rollback" to an older version you should use checkout the git-checkout command. maybe the git reset -–hard HEAD is okay to include... but it won't be immediately obvious to new users why it does what it does... this nomenclature was likely not the best choice whenever it was made.
gl with your gitting.
whiteside
u're talking sdf
On Sat, Dec 27, 2008 at 5:29 PM, Zorba <cr@altmore.co.uk> wrote:
Show 30 quoted lines
> > tidied up the formatting, added a few more comments where needed, fixed > errors/lack of clarity > > "Zorba" <cr@altmore.co.uk> wrote in message > news:gj68a0$u56$3@ger.gmane.org... > > Here is a little exercise / tutorial / warm-up for someone starting out > > with Git. If you're anyting like me you may find the tutorials etc. on > > git.or.cz a bit daunting. I recommend you try this after reading the user > > manual but before tearing your hair out trying to follow all the examples > > in the user manual. After you've followed this simple workflow, then go > > back to the more advanced stuff in the tutorials and user manuals (like > > cloning repositories and creating and merging branches). > > > > I created this exercise to try and model our workflow and what we wanted > > to use git for = tracking a project with multiple files where the filebase > > might change frequently from one version to the next. > > > > http://siliconmouth.wordpress.com/category/nerdy/ > > > > look for December 27, 2008 or "git warmup" > > > > > > > > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html