From: Frans Klaver <fransklaver@gmail.com>
To: Angelo Borsotti <angelo.borsotti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git gui does not open bare repositories
Date: Fri, 28 Sep 2012 10:08:20 +0200 [thread overview]
Message-ID: <CAH6sp9N1cFH7orPNmfbhgHq6oUNtQNe=-5f5jkYNXzr+6Xp_pQ@mail.gmail.com> (raw)
In-Reply-To: <CAB9Jk9CA+e8xR9sz7cW+5+990FmTeYN3pjxs4ZKFpkzb6OL35Q@mail.gmail.com>
On Fri, Sep 28, 2012 at 9:50 AM, Angelo Borsotti
<angelo.borsotti@gmail.com> wrote:
> I have created a bare repository:
>
> $ mkdir remote.git
>
> angelo@ANGELO-PC /d/gtest (master)
> $ git init --bare
> Initialized empty Git repository in d:/gtest/
This creates a bare repository in d:/gtest, not in
d:/gtest/remote.git. You'll need to cd into remote.git to create a
bare repo.
> and then tried to open it with the git gui, but have got the message:
> "remote.git is not a git repository".
So this message is correct.
Be as it may, as soon as you've initialized the repo as required, git
gui will (probably) tell you:
"Cannot use bare repository:
d:/gtest/remote.git"
So nothing gained there. So I'm wondering what you expect git gui to
give you in a bare repo? It seems to me that this tool is specifically
aimed at non-bare repos, allowing for creating commits, merges and
whatnot; all things you cannot typically do in a bare repo.
Frans
next prev parent reply other threads:[~2012-09-28 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 7:50 git gui does not open bare repositories Angelo Borsotti
2012-09-28 8:08 ` Frans Klaver [this message]
[not found] ` <CAB9Jk9BivVrH7daMR=u5Y6Ut=pZGRBcgKNZ_afZ53XFxhFBnZw@mail.gmail.com>
2012-09-28 8:35 ` Frans Klaver
2012-09-28 8:44 ` Stefan Näwe
2012-09-28 8:56 ` Angelo Borsotti
2012-09-28 12:09 ` Angelo Borsotti
2012-09-28 14:15 ` Ben Smith-Mannschott
2012-09-28 16:46 ` Angelo Borsotti
2012-09-28 19:43 ` Ben Smith-Mannschott
2012-09-28 18:22 ` Angelo Borsotti
2012-10-01 6:22 ` Stefan Näwe
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='CAH6sp9N1cFH7orPNmfbhgHq6oUNtQNe=-5f5jkYNXzr+6Xp_pQ@mail.gmail.com' \
--to=fransklaver@gmail.com \
--cc=angelo.borsotti@gmail.com \
--cc=git@vger.kernel.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).