From: Diego Calleja <diegocg@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: jes@sgi.com, pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: git for dummies, anyone?
Date: Thu, 9 Feb 2006 16:35:46 +0100 [thread overview]
Message-ID: <20060209163546.493334f8.diegocg@gmail.com> (raw)
In-Reply-To: <43EB4F05.8090400@pobox.com>
El Thu, 09 Feb 2006 09:17:41 -0500,
Jeff Garzik <jgarzik@pobox.com> escribió:
> Check out:
> http://linux.yyz.us/git-howto.html
That is a nice guide, but is oriented to developers, I think jes
was asking from a user POV (I've needed to google for such things
several times) ie how to switch to a given tag and return to master,
how to update the repository periodically, etc; no stuff about how to
manage patches. It may be nice to see such thing on your guide, something
like this:
- How to get a copy of linus'tree
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
- Update your copy:
cd linux-2.6; git pull; git pull --tags
- How to go back to a certain snapshot
git reset --hard v2.6.13 (ls .git/refs/tags to see all the tags). Not the
cleanest method, I think. "git-checkout -f master" will return to the "head"
of the repository. You can also pass commit-IDs to git-reset instead of tags?
- bisect search
git reset --hard BrokenVersion
git bisect start
git bisect good v2.6.13-rc2
Compile, test, and do "git bisect good" or "git bisect bad" until you find
the culprit. If it doesn't compile or something you can do a "git bisect good/bad"
"git bisect reset" resets the repository when you are done.
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
explains it with more detail.
next prev parent reply other threads:[~2006-02-09 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 15:03 How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git Paul Jackson
2006-02-08 15:14 ` Dale Farnsworth
2006-02-08 15:27 ` Paul Jackson
2006-02-08 15:15 ` Mattia Dongili
[not found] ` <20060208101626.3afa69ba.seanlkml@sympatico.ca>
2006-02-08 15:16 ` sean
2006-02-08 17:53 ` Bryan O'Sullivan
2006-02-08 18:06 ` Paul Jackson
2006-02-09 13:08 ` git for dummies, anyone? (was: Re: How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git) Jes Sorensen
2006-02-09 14:17 ` git for dummies, anyone? Jeff Garzik
2006-02-09 14:36 ` Josh Boyer
2006-02-09 14:43 ` Jes Sorensen
2006-02-09 14:55 ` Paul Jackson
2006-02-09 16:46 ` Catalin Marinas
2006-02-09 15:35 ` Diego Calleja [this message]
2006-02-09 15:56 ` Jes Sorensen
2006-02-09 16:07 ` J. Bruce Fields
2006-02-09 16:37 ` Marc Koschewski
2006-02-09 14:50 ` git for dummies, anyone? (was: Re: How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git) Paul Jackson
2006-02-09 23:16 ` Willy Tarreau
2006-02-10 0:03 ` Paul Jackson
2006-02-10 6:23 ` Willy Tarreau
2006-02-10 14:08 ` Theodore Ts'o
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=20060209163546.493334f8.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=jes@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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
Powered by JetHome