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

Re: [PATCHv3 0/3] git-gui: more robust handling of fancy repos

From
Bert Wesarg <bert.wesarg@googlemail.com>
Date
Dec 6, 2009, 12:59 UTC
Message-ID
<36ca99e90912060459u1073288bj2114f8ab56c7224b@mail.gmail.com>
In-Reply-To
<cb7bb73a0912060014p548884e0g8c4510a5b562901b@mail.gmail.com>

On Sun, Dec 6, 2009 at 09:14, Giuseppe Bilotta <giuseppe.bilotta@gmail.com> wrote:

Show 10 quoted lines
> On Tue, Oct 27, 2009 at 12:35 PM, Bert Wesarg
> <bert.wesarg@googlemail.com> wrote:
>>
>> I would also suggest to always export GIT_DIR into the environment, so
>> that guitools can relay on this.
>
> I'm sorry I couldn't reply to this email earlier. I have never used
> this feature, but if you can provide some example guitools
> configuration I'll gladly move the environment export earlier and test
> it.
Here it is:
[guitool "exclude/Ignore file"]
	cmd = echo \"$FILENAME\" >> \"${GIT_DIR:=.git}/info/exclude\"
	noconsole = yes
	needsfile = yes

The purpose is simple: add the current file to the info/exclude file in the git dir As you can see, I have a workaround for not having GIT_DIR in the env, which should solve the issue. But it would be nice to rely on this.

Bert
>
> --
> Giuseppe "Oblomov" Bilotta
>
Previous: Giuseppe BilottaNext: Giuseppe Bilotta
Message 7 of 9 in “[PATCHv3 0/3] git-gui: more robust handling of fancy repos”
  1. Giuseppe BilottaAug 16, 2009
  2. 1/3 git-gui: handle non-standard worktree locationsGiuseppe Bilotta, Aug 16, 2009
  3. 2/3 git-gui: handle bare repos correctlyGiuseppe Bilotta, Aug 16, 2009
  4. 3/3 git-gui: work from the .git dirGiuseppe Bilotta, Aug 16, 2009
  5. Bert WesargOct 27, 2009
  6. Giuseppe BilottaDec 6, 2009
  7. Bert WesargDec 6, 2009
  8. Giuseppe BilottaDec 6, 2009
  9. Shawn O. PearceDec 5, 2009

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.