From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joost Diepenmaat Newsgroups: gmane.emacs.help Subject: Re: Which git front-end in emacs is better? Date: Thu, 23 Oct 2008 11:18:36 +0200 Organization: Zeekat Softwareonwikkeling Message-ID: <87d4hrbrf7.fsf@zeekat.nl> References: <29de18070810210438x2d7f3b6dhd95d34621091eb4f@mail.gmail.com> <200810220025.m9M0PK2w018836@zogzog.maillard.mobi> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1224754966 15586 80.91.229.12 (23 Oct 2008 09:42:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Oct 2008 09:42:46 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Oct 23 11:43:46 2008 connect(): Connection refused Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KswjJ-0003tB-6i for geh-help-gnu-emacs@m.gmane.org; Thu, 23 Oct 2008 11:43:45 +0200 Original-Received: from localhost ([127.0.0.1]:57922 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KswiD-0006tO-Ic for geh-help-gnu-emacs@m.gmane.org; Thu, 23 Oct 2008 05:42:37 -0400 Original-Path: news.stanford.edu!headwall.stanford.edu!news.glorb.com!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAABgAAAAwBAMAAAD5pqeQAAAAAXNSR0IArs4c6QAAABhQTFRF URgKoyIAmTMXqF5KuYl7y6ui4NDM+/r4zJNdmwAAAAFiS0dEAIgFHUgAAAAJcEhZcwAACxMAAAsT AQCanBgAAAAHdElNRQfXDBIUAgGiEa2aAAABYUlEQVQoz02SvXaDMAyF3aHdZegD2PxkJhQ8J4R6 juGUuZDUe43R61eGJA0D8B1dXV0LGCJaDDePyOjZBtT9MgSYbIu+UpNl2A+/ukPXfNUku2ROdWhM 99myqzWX3Czp8dhY1n+MfWau+X4fZGNZpecuSwpFMHOZnpskFppgEaksGs5lFoYeYilOEMkjzcGC CzjxJJoowZIAQMPhfdYEecGhBFCOwO9GKkFkXZDtfIAax2C9wwKAWzwFyPGwQrXCIkimbzAHeFtl Ts0vJHvFkRI01ssVwpyMAoHkGmfFqL+TEmSNXjHMXeiHZAjZqjOsVxxSV8UG3Fi2ZGID2Fs2t7d3 6mLTdIdUM+PuECvW/T6gfobnSqTY+DDgmrnmATSnfMiQrTvcDOikyT1OWHxZPIF8As8P/waOjzdn IGt+vRVgYD7CrakFTSfFbwAB0Y+ghWj0IjP0Scz6I2E3zIlFb/8AfR6DwKVgwNYAAAAASUVORK5C YII= Cancel-Lock: sha1:GC36+0KlIvR5doZ5LspPxXgmjBg= Original-Lines: 49 Original-NNTP-Posting-Host: 80.126.3.69 Original-X-Trace: 1224753570 news.xs4all.nl 186 [::ffff:80.126.3.69]:58397 Original-X-Complaints-To: abuse@xs4all.nl Original-Xref: news.stanford.edu gnu.emacs.help:163718 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:59059 Archived-At: Richard Riley writes: > Lave writes: > >> I have no experience of using VC, I just want a interface for git. >> >> Git.el saids allow user to use full functionality of Git. But I found >> Magit having more. I'll try Magit first. >> >> Thanks you all. > > A little OT, but ... > > 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? All the advice I've heard so far indicates that you should use different repos for different projects (or sub-projects, if it's a large project). This makes it easier to clone out just what you want, and can make some operations quicker. Also, it just makes sense :-) > 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. If you're the only person working on a project, you don't need to have the repo remotely accessible. Note that *everybody* gets a *complete* repository - so a remote/centralized repo is mostly useful if you want to people be able to clone "your" repository, and/or push back their changes without manual interference. Also: you can commit / branch etc to your own repo as much as you like, and you only need to merge/push your stuff to the "main" repo (if there is one) once you're ready with that branch. > This is a start but is svn orientated, but any other pointers > appreciated preferably without svn and only using git. You may want to check out the documentation on github.com: it has lots of practical day-to-day tips: http://github.com/guides/home -- Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/