git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "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 13:06:11 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703301256230.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0703302135590.10784@poirot.grange>



On Fri, 30 Mar 2007, Guennadi Liakhovetski wrote:
> 
> 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...

There's a conversion script to help you convert in place if you care.

Look at the git list for an email that looks something like this:

	Date: Wed, 14 Mar 2007 02:16:12 -0400
	From: Shawn O. Pearce <spearce@spearce.org>
	To: git@vger.kernel.org
	Subject: Upgrade to 1.5.0 utility

	Yesterday on #git DrNick wanted a script to update a pre-1.5.0
	Git repository to be like a 1.5.0 (and later) style repository.
	...

which has a script in it to do this (it uses another script that is 
already in git/contrib/ that just moves all the ".git/remotes" entries 
as-is from the remotes files into the .git/config file)

I haven't tested it myself, so caveat emptor. But the config file format 
really isn't *that* complicated - do the conversion with the script, and 
then just go back and look at .git/config and verify that it looks sane, 
or edit it to match your taste.

		Linus

  reply	other threads:[~2007-03-30 20:06 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 [this message]
2007-03-30 20:23                 ` Theodore Tso
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

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

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0703301256230.6730@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 NNTP newsgroup(s).