All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [RFC] require-work-tree wants more than what its name says
Date: Thu, 05 May 2011 10:31:08 -0700	[thread overview]
Message-ID: <7v39kt9hr7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTinaoopUxOHC0XaUxMLXj4pCXND+UA@mail.gmail.com> (Sverre Rabbelier's message of "Thu, 5 May 2011 13:15:29 +0200")

Sverre Rabbelier <srabbelier@gmail.com> writes:

> So do we need more tests for git-submodule to find out, or is this a
> hint to the submodule people to chime in? If so, should they be cc-ed?

I could queue a version without any conversion of in-tree users, so that
stakeholders can verify and convert their use of require-work-tree to the
new saner alternative one by one.  Actually I tend to like that better.

I am not convinced myself if it is a sane use case to run "git pull" from
a totally random place and let fetch and merge magically happen somewhere
completely unrelated to your current working directory only because you
have GIT_DIR and GIT_WORK_TREE set to begin with.  After getting into a
habit of relying on these environment variables so much that you do not
even think about their existence, you will reach a point where you have no
idea where to go offhand when a merge conflict actually happens and you
have to go there to fix things up.

  reply	other threads:[~2011-05-05 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 23:33 [RFC] require-work-tree wants more than what its name says Junio C Hamano
2011-05-04  7:38 ` Jeff King
2011-05-04 15:42   ` Junio C Hamano
2011-05-04 21:28     ` Jeff King
2011-05-05  2:11       ` Junio C Hamano
2011-05-05  4:23         ` Jeff King
2011-05-05  4:28           ` Jeff King
2011-05-05 11:15         ` Sverre Rabbelier
2011-05-05 17:31           ` Junio C Hamano [this message]
2011-05-04  8:47 ` Michael J Gruber
2011-05-04  8:50   ` Jeff King
2011-05-04 15:47     ` 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=7v39kt9hr7.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=srabbelier@gmail.com \
    /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.