From: Chris Willard <chris@thewillards.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Which git front-end in emacs is better?
Date: Fri, 14 Nov 2008 15:02:17 +0000 [thread overview]
Message-ID: <20081114150217.GB28697@uts.thewillards.local> (raw)
In-Reply-To: <gdo51e$90p$1@registered.motzarella.org>
On Wed, 22 Oct 2008, Richard Riley wrote:
[snip]
> I would be interested in which tutorials people used to learn how best
> to use GIT. I've found plenty of examples of how it works, but none of
> how to work *with* it. e.g A programmer has 3 main directory hierarchies
> he wishes to control. Do all 3 go in one repository? Where does that
> repository reside? Local? Remote? Does one need to check in /out etc -
> I'm sure its out there but its hard to find beneath all the explanations
> tend to concentrate on that which the user doesn't generally care about
> such as how git stores "blobs" and how it hashes file names etc.
[snip]
Hello Richard,
Try http://www-cs-students.stanford.edu/~blynn/gitmagic/ for a simple
look at git. From other tutorials I could see what git could do but
was still a little confused. This helped.
Regards,
Chris.
--
oOoOo "Spamby! Do not put in mouth or rectum." - HCTV oOoOo
oOoOo oOoOo
oOoOo oOoOo
oOoOo oOoOo
--
This message was scanned by ESVA and is believed to be clean.
next prev parent reply other threads:[~2008-11-14 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 11:38 Which git front-end in emacs is better? Lave
2008-10-21 21:03 ` Nikolaj Schumacher
2008-10-22 0:25 ` Xavier Maillard
2008-10-22 10:24 ` Lave
[not found] ` <mailman.1782.1224671087.25473.help-gnu-emacs@gnu.org>
2008-10-22 21:13 ` Richard Riley
2008-10-23 9:18 ` Joost Diepenmaat
2008-10-23 14:35 ` Jonathan Groll
2008-10-28 11:39 ` Lave
2008-11-14 15:02 ` Chris Willard [this message]
[not found] <mailman.1681.1224589095.25473.help-gnu-emacs@gnu.org>
2008-10-21 18:44 ` Wei Weng
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081114150217.GB28697@uts.thewillards.local \
--to=chris@thewillards.co.uk \
--cc=help-gnu-emacs@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).