From: Andy Parkins <andyparkins@gmail•com>
To: git@vger•kernel.org
Subject: Re: What's in git.git and announcing GIT v1.5.0-rc1
Date: Fri, 12 Jan 2007 15:01:07 +0000 [thread overview]
Message-ID: <200701121501.24642.andyparkins@gmail.com> (raw)
In-Reply-To: <7v8xg9x8uu.fsf@assigned-by-dhcp.cox.net>
On Friday 2007, January 12 02:43, Junio C Hamano wrote:
> - I'll change my $PATH to use the 'master' version, not 'next',
> for my own use until v1.5.0 final. I ask people who usually
> follow 'next' to do the same so that we can catch breakages
> on 'master'.
Minor thing: git-rebase, git-cherry-pick and git-pull (and presumably
git-merge) all need to be the repository root to work. If that is
intentional, a better message than "fatal: Not a git repository: '.git'"
would be appropriate.
For me, I'd prefer that they worked in subdirectories. I do all almost all
development in "src/" and having to change up a directory just to run git
commands is inconvenient.
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail•com
next prev parent reply other threads:[~2007-01-12 15:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 2:43 What's in git.git and announcing GIT v1.5.0-rc1 Junio C Hamano
2007-01-12 3:59 ` [PATCH] reflog-expire: brown paper bag fix Junio C Hamano
2007-01-12 4:02 ` Shawn O. Pearce
2007-01-12 15:01 ` Andy Parkins [this message]
2007-01-12 18:35 ` [PATCH] Friendlier error message for commands that can't be run from a subdirectory koreth
2007-01-12 18:39 ` What's in git.git and announcing GIT v1.5.0-rc1 Steven Grimm
2007-01-12 19:10 ` [PATCH] Change to the repository's root directory if needed koreth
2007-01-12 21:18 ` Junio C Hamano
2007-01-12 22:11 ` Steven Grimm
2007-01-12 23:17 ` Junio C Hamano
2007-01-12 20:26 ` [PATCH] Explain "Not a git repository: '.git'" Junio C Hamano
2007-01-12 20:55 ` Junio C Hamano
2007-01-12 20:55 ` [PATCH 1/3] Define cd_to_toplevel shell function in git-sh-setup Junio C Hamano
2007-01-12 20:55 ` [PATCH 2/3] Use cd_to_toplevel in scripts that implement it by hand Junio C Hamano
2007-01-12 20:56 ` [PATCH 3/3] Allow whole-tree operations to be started from a subdirectory Junio C Hamano
2007-01-13 16:42 ` Andy Parkins
2007-01-14 0:11 ` Josef Weidendorfer
2007-01-14 0:21 ` Shawn O. Pearce
2007-01-14 0:39 ` Josef Weidendorfer
2007-01-14 0:50 ` Junio C Hamano
2007-01-14 0:52 ` Steven Grimm
2007-01-14 1:37 ` Junio C Hamano
2007-01-14 18:13 ` Steven Grimm
2007-01-14 18:29 ` Steven Grimm
2007-01-14 19:36 ` Junio C Hamano
2007-01-14 1:50 ` Junio C Hamano
2007-01-16 15:14 ` Andreas Ericsson
2007-01-14 23:36 ` What's in git.git and announcing GIT v1.5.0-rc1 lamikr
2007-01-15 2:21 ` Horst H. von Brand
2007-01-15 20:54 ` lamikr
2007-01-15 21:56 ` Junio C Hamano
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=200701121501.24642.andyparkins@gmail.com \
--to=andyparkins@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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