All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Richard" <richard@webdezign.co.uk>
Cc: <git@vger.kernel.org>
Subject: Re: Moving git
Date: Fri, 16 Oct 2009 18:11:58 +0200	[thread overview]
Message-ID: <vpqbpk71fox.fsf@bauges.imag.fr> (raw)
In-Reply-To: <8440EA2C12E50645A68C4AA988716651244654@SERVER.webdezign.local> (richard@webdezign.co.uk's message of "Fri\, 16 Oct 2009 16\:45\:24 +0100")

"Richard" <richard@webdezign.co.uk> writes:

> Hi Matthieu,
>
>
> Thanks for replying.
>
> Basically, I used git-svn to import from git. I'm trying to get rid of
> the origin branch. (I probably should have used the no-metdata switch).
>
> The command I used was
>
> git branch prune origin
>
> I tried "git remote rm origin" which worked on my local win32 machine,
> but the linux server I was working on did not recognise "git remote rm".
>
> I'm pretty sure git stores the current git directory as I've seen the
> --git-dir and --work-tree environment variables.

Git doesn't store them by default for the current repository. "git
rev-parse --git-dir" guesses where your .git/ directory is (looking
for ./.git/, ../.git, and so on). OTOH, Git stores URLs for remote
repositories (see .git/config).

> Plus I also noticed on msysgit gives " Local uncommitted changes,
> not checked in to index" sometimes, when I move the directory.

I don't know msysgit, but I guess you'll have problems if your
repository is on a FAT filesystem. Is it the case?

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2009-10-16 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 14:58 Moving git Richard Lee
2009-10-16 15:17 ` Matthieu Moy
2009-10-16 15:45   ` Richard
2009-10-16 16:11     ` Matthieu Moy [this message]
2009-10-16 15:41 ` Santi Béjar
2009-10-16 17:04 ` Richard Lee
2009-10-16 17:10   ` Matthieu Moy
2009-10-16 18:42   ` Todd Zullinger
2009-10-19  9:30     ` rhlee
2009-10-20 16:33 ` Daniel Barkalow
2009-10-20 16:37   ` Richard

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=vpqbpk71fox.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=richard@webdezign.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.