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

Re: [PATCH] gitk: new option to hide remote refs

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 4, 2009, 06:28 UTC
Message-ID
<7vab2g6qkd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<55b7e43bcd59aa64c70edde83ac87147aa0091bb.1249336225.git.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
Show 9 quoted lines
> @@ -1689,7 +1690,7 @@ proc readrefs {} {
>  	if {![string match "refs/*" $ref]} continue
>  	set name [string range $ref 5 end]
>  	if {[string match "remotes/*" $name]} {
> -	    if {![string match "*/HEAD" $name]} {
> +	    if {![string match "*/HEAD" $name] && !$hideremotes} {
>  		set headids($name) $id
>  		lappend idheads($id) $name
>  	    }

Hmm, I wonder if it would be more useful to extend this by using $skiprefs pattern instead, like so:

>  	if {![string match "refs/*" $ref]} continue
>  	set name [string range $ref 5 end]
+	if {$skiprefs != "" && [string match $skiprefs $name]} continue
>  	if {[string match "remotes/*" $name]} {
> 	    if {![string match "*/HEAD" $name]} {
	...
Previous: Thomas RastNext: Thomas Rast
Message 2 of 6 in “gitk: new option to hide remote refs”
  1. gitk: new option to hide remote refsThomas Rast, Aug 3, 2009
  2. Junio C HamanoAug 4, 2009
  3. Thomas RastAug 4, 2009
  4. Santi BéjarAug 4, 2009
  5. Thell FowlerAug 10, 2009
  6. Paul MackerrasAug 13, 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.