All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Goerzen <jgoerzen@complete.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Sean <seanlkml@sympatico.ca>, git@vger.kernel.org
Subject: Re: git-relink doesn't work on bare repos
Date: Tue, 4 Mar 2008 09:19:19 -0600	[thread overview]
Message-ID: <200803040919.19641.jgoerzen@complete.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803041501500.22527@racer.site>

On Tue March 4 2008 9:03:15 am Johannes Schindelin wrote:
> Hi,
>
> On Tue, 4 Mar 2008, John Goerzen wrote:
> > On Tue March 4 2008 1:09:59 am Sean wrote:
> > > repos follow the general naming convention of ending in .git relink
> > > will work.  That is, if your bare repos are named repo.git rather than
> > > just repo.
> >
> > I never do that because I think it's silly to have to type .git
> > everytime ;-)
>
> Well, it is a convention, and if you choose not to follow it, that's what
> you get.

That's not documented anywhere.

I mean, git is plubming, right?  I should be able to call it myrepo.exe if I 
like, and as long as it has a .git dir with stuff in it, or is bare, it 
should just work.

> > If I give people a git:// url, they already know it's a Git repo, I
> > figure.
>
> So you must use "--git-dir" _everytime_ you are working with Git inside
> the repo.

That's not been my experience.  In fact, I can 'git log' quite happily inside 
a bare repo.  Why on earth should git-relink care what I have named my repo?  
It's not like git clone, push, pull, or anything else cares.

-- John

      reply	other threads:[~2008-03-04 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  0:29 git-relink doesn't work on bare repos John Goerzen
2008-03-04  7:09 ` Sean
2008-03-04 14:34   ` John Goerzen
2008-03-04 15:03     ` Johannes Schindelin
2008-03-04 15:19       ` John Goerzen [this message]

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=200803040919.19641.jgoerzen@complete.org \
    --to=jgoerzen@complete.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    /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.