git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: basics... when reading docs doesn't help
Date: Fri, 30 Mar 2007 16:23:12 -0400	[thread overview]
Message-ID: <20070330202312.GG3198@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0703302135590.10784@poirot.grange>

On Fri, Mar 30, 2007 at 09:49:20PM +0200, Guennadi Liakhovetski wrote:
> Aha, so, that's how it is then! Why hasn't anybody explained this to me 
> strait away?!:-))))

A lot of this is in the git 1.5's User Manual:

	http://www.kernel.org/pub/software/scm/git/docs/user-manual.html

See also the man page for git-remote, or here:

	http://www.kernel.org/pub/software/scm/git/docs/git-remote.html


> Yeah, hopefully, I'll learn to at least use this thing efficiently enough. 
> Someone has to write a book on it though...

The user-manual and the git tutorials are pretty good --- just make
sure you look at the ones that come with git 1.5.0, or the ones at
http://www.kernel.org/pub/software/svm/git/docs (which reflects the
Documentation as of the latest development version of git).

The problem is that there are some tutorials on the web which assume
git 1.4.x, or cogito, and that has been listed as a defect by people
who have been confused because those tutorials are out of date with
respect to modern git.[1]

[1] http://changelog.complete.org/posts/594-More-on-Git,-Mercurial,-and-Bzr.html

> And, so, it's a pity I cloned Paul's tree yesterday with the "old" git. 
> And from your answer above it seems like some features of the "new" git 
> will not be available with this tree, like equally named local and remote 
> branches, etc. There isn't a way to convert such a "old style" tree to the 
> "new style", is there? Not a big deal, will re-clone at some point, maybe 
> when we get local git mirrors...

Yeah, we need to really make sure the word gets out that new git users
should really make sure they are using git 1.5, and not git 1.4.x; it
is such an improvement in terms of usability over git 1.4.x that there
really is no comparison.  (Of course, guess what Debian is going to
ship in their soon-to-be-release "stable" distribution?  git 1.4.4.  Sigh...)

It is possible to get the new style naming, by using the git remote
command.  Just do

	git remote add origin <url>

...and that will adjust your git configuration file appropriate.
Check out the git 1.5.0 release notes, and the git-config man page,
and there are some other adjustments you can make as well that will
make git more efficiently, at the cost of breaking some level of
compatibility with git 1.4.x tools which replicate via the "dumb" http
protocol.  But for local development repositories that generally isn't
a concern.

						- Ted

  parent reply	other threads:[~2007-03-30 20:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 20:50 basics... when reading docs doesn't help Guennadi Liakhovetski
2007-03-29 21:16 ` J. Bruce Fields
2007-03-29 21:26   ` Junio C Hamano
2007-03-29 21:46     ` J. Bruce Fields
2007-03-29 22:13       ` Guennadi Liakhovetski
2007-03-29 22:35         ` Linus Torvalds
2007-03-30 18:16           ` Guennadi Liakhovetski
2007-03-30 18:48             ` Linus Torvalds
2007-03-30 19:49               ` Guennadi Liakhovetski
2007-03-30 20:06                 ` Linus Torvalds
2007-03-30 20:23                 ` Theodore Tso [this message]
2007-03-30 20:39                 ` Junio C Hamano
2007-03-30 21:11                   ` Guennadi Liakhovetski
2007-03-30  2:43         ` Theodore Tso
2007-03-30 14:49           ` J. Bruce Fields
2007-03-30 18:02         ` Andreas Herrmann
2007-03-30 18:24           ` Guennadi Liakhovetski
2007-03-29 22:27   ` Matthieu Moy

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070330202312.GG3198@thunk.org \
    --to=tytso@mit.edu \
    --cc=bfields@fieldses.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).