git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 3/3] Allow whole-tree operations to be started from a subdirectory
Date: Sat, 13 Jan 2007 16:42:15 +0000	[thread overview]
Message-ID: <200701131642.16824.andyparkins@gmail.com> (raw)
In-Reply-To: <7vac0orml9.fsf_-_@assigned-by-dhcp.cox.net>

On Friday 2007, January 12 20:56, Junio C Hamano wrote:

> This may not actually be what we want to do.  These commands are
> inherently whole-tree operations, and an inexperienced user may
> mistakenly expect a "git pull" from a subdirectory would merge
> only the subdirectory the command started from.

You're right it might be confusing at first, however, I still think it's the 
right thing to do.

Here's my reasoning: for a while, with subversion as a user you feel all warm 
inside that commands only work on the current subdirectory, so "svn update" 
would only update the current subdirectory to the latest revision.  Of course 
as git users we all see the horrendous potential errors that behaviour can 
induce.  It creates subdirectories with mixed versions from the repository - 
absolute disaster pends.

Git is of course far more sensible, if you checkout in a subdirectory the 
whole working directory changes, meaning everything is always nicely in sync 
and really does represent a snapshot at any time.

Now; once you (as a new user) accept that git checkout should (and does) 
checkout the whole working directory regardless of where you are, then by 
extension every other working-directory-wide command should do the same.

Phew.  I'm too noisy.  What a verbose way of saying
   fromAOL("me too");


Andy

-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com

  reply	other threads:[~2007-01-13 16:45 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 ` What's in git.git and announcing GIT v1.5.0-rc1 Andy Parkins
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 [this message]
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=200701131642.16824.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).