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

Re: Re: [PATCH 3/3] git-gui: new config to control staging of untracked files

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Oct 17, 2011, 19:27 UTC
Message-ID
<20111017192706.GB3168@sandbox-rc>
In-Reply-To
<CAKPyHN3pKUSLTs8_5QMo5i+=3w7KXAHJjDOfQ1XYG92ZbQ1SeA@mail.gmail.com>
Hi,
On Mon, Oct 17, 2011 at 08:47:50PM +0200, Bert Wesarg wrote:
Show 12 quoted lines
> On Mon, Oct 17, 2011 at 20:34, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> > Here I am wondering whether we have a similar mechanism in git gui like
> > in core git that makes yes,true,1 equivalents (and similar with other
> > values) ?
> 
> But it is not only yes,true,1 or no,false,0 its a tristate with the
> third state 'ask'. For booleans, there is such functionality in git
> gui. See is_config_true and is_config_false. Reusing these for this
> tristate wouldn't work. The current check here is indeed very strict
> and should be loosen by at least ignoring the case, surrounding
> spaces, and allow also true/false. But also note, that this variable
> can be set via the Options menu, so you can't mistype it.

Well if using git config you can ;-). I just wanted to ask whether we may already have machinery which supports such tristate. If we do not I think the current "strict" configuration is fine. In most cases the user will use the gui itself to configure such behavior so thats no big deal. If someone needs that it can be added later on.

Thanks, Heiko
Previous: Bert WesargNext: Pat Thoyts
Message 6 of 9 in “git-gui: fix unintended line break in message string”
  1. 1/3 git-gui: fix unintended line break in message stringBert Wesarg, Oct 14, 2011
  2. 2/3 git-gui: use "untracked" for files which are not known to gitBert Wesarg, Oct 14, 2011
  3. 3/3 git-gui: new config to control staging of untracked filesBert Wesarg, Oct 14, 2011
  4. Heiko VoigtOct 17, 2011
  5. Bert WesargOct 17, 2011
  6. Heiko VoigtOct 17, 2011
  7. Pat ThoytsOct 17, 2011
  8. Bert WesargOct 18, 2011
  9. Pat ThoytsOct 18, 2011

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.