git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git pull and GIT_DIR

From
Junio C Hamano <gitster@pobox.com>
Date
May 2, 2012, 19:11 UTC
Message-ID
<7v62ceiejp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120502142536.GA2609@debian.b2j>
bill lam <cbill.lam@gmail.com> writes:
Show 12 quoted lines
> It appeared that
>
> a)
> cd /path/to && git pull git/https://....
>
> will fetch and checkout latest changes to working tree.  This is as
> expected.  On the contrary
>
> b)
> GIT_DIR=/path/to/.git git pull git/https://....
>
> will ...
-ETOOLITTLEINFO.
When you do b)
 - is /path/to the working tree for /path/to/.git?
 - where is your $(pwd)?
 - if your $(pwd) is different from /path/to, how are you telling git
   where the working tree is?  are you using GIT_WORK_TREE or something?
Previous: bill lamNext: bill lam
Message 2 of 3 in “git pull and GIT_DIR”
  1. bill lamMay 2, 2012
  2. Junio C HamanoMay 2, 2012
  3. bill lamMay 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.