From: Theodore Tso <tytso@mit.edu>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 3/4] Automatically detect a bare git repository.
Date: Sun, 31 Dec 2006 07:52:05 -0500 [thread overview]
Message-ID: <20061231125205.GB14286@thunk.org> (raw)
In-Reply-To: <20061231043019.GC5823@spearce.org>
On Sat, Dec 30, 2006 at 11:30:19PM -0500, Shawn O. Pearce wrote:
> Many users find it unfriendly that they can create a bare git
> repository easily with `git clone --bare` but are then unable to
> run simple commands like `git log` once they cd into that newly
> created bare repository. This occurs because we do not check to
> see if the current working directory is a git repository.
Thanks for coding this up!
If you do this, does this mean that we can also eliminate the global
variable --bare, since git will be able to figure out we're in a bare
repository all by itself?
- Ted
next prev parent reply other threads:[~2006-12-31 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ffc8ddd9b500c2a34d2bd6ba147dc750d951bcd.1167539318.git.spearce@spearce.org>
2006-12-31 4:29 ` [PATCH 2/4] Replace "GIT_DIR" with GIT_DIR_ENVIRONMENT Shawn O. Pearce
2006-12-31 4:30 ` [PATCH 3/4] Automatically detect a bare git repository Shawn O. Pearce
2006-12-31 5:09 ` Junio C Hamano
2006-12-31 5:26 ` Shawn Pearce
2006-12-31 5:46 ` Junio C Hamano
2006-12-31 12:52 ` Theodore Tso [this message]
2007-01-01 21:01 ` Shawn O. Pearce
2006-12-31 17:54 ` Martin Waitz
2007-01-01 20:57 ` Shawn O. Pearce
2006-12-31 4:32 ` [RFC/PATCH 4/4] Disallow working directory commands in a bare repository Shawn O. Pearce
2006-12-31 5:33 ` Junio C Hamano
2006-12-31 6:11 ` Shawn O. Pearce
2006-12-31 8:01 ` Junio C Hamano
2006-12-31 12:49 ` Theodore Tso
2006-12-31 15:13 ` Johannes Schindelin
2006-12-31 19:19 ` Junio C Hamano
2007-01-02 21:42 ` Johannes Schindelin
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=20061231125205.GB14286@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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.
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).