All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
	Andy Parkins <andyparkins@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 3/3] Allow whole-tree operations to be started from a subdirectory
Date: Sun, 14 Jan 2007 10:13:53 -0800	[thread overview]
Message-ID: <45AA72E1.6060701@midwinter.com> (raw)
In-Reply-To: <7virfaie1m.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> I consider that being in a subdirectory means the user is in the
> middle of actively working on something in that area.  Honestly
> I do not understand why anybody would want to run the five
> whole-tree commands under discussion (merge, pull, rebase,
> revert and cherry-pick) in the middle of doing something, so
> from the theoretical point of view I would agree that it makes
> sense for the commands to internally cd-up to do their work, I
> am not sure how much practical value it would add.
>   

Here's one use case for merge/pull/rebase that is, if not an everyday 
thing, then at least fairly common in my group: Person B fixes a bug in 
some code that's causing problems for the code person A is working on. 
Person A is not at a stopping point in his own work yet, but wants to 
get the fix.

Revert and cherry-pick are less common here but consider this: some 
people want submodule support because they're working on a specific part 
of the tree. They only cd into a subdirectory because there's no way for 
them to make that subdirectory the top level of their local repository. 
The fact that there are siblings of their current directory is just an 
artifact of the project layout and has nothing to do with what they're 
doing at the moment.

For example, on a simple Web project, the UI designers will always cd to 
the "html" directory. They get "src" and "lib" too, but if they had a 
choice they wouldn't. When they cherry-pick, it'll always be a 
cherry-pick of their own stuff (in the html directory) and likewise with 
a revert, so they have no reason to cd-up for any of those operations if 
the tool doesn't demand it. And perhaps less obvious: in a typical 
shared integration area setup, they will never have any conflicts 
anywhere but their subdirectory since the other directories will always 
be able to fast-forward merge. So cd-up isn't useful for them even in 
the case of merge conflicts.

-Steve

  reply	other threads:[~2007-01-15 17:21 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
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 [this message]
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=45AA72E1.6060701@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=Josef.Weidendorfer@gmx.de \
    --cc=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 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.