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

cosmetic bug in gitk cherry-pick

From
PCPeter Cordes <peter@cordes.ca>
Date
May 10, 2009, 03:36 UTC
Message-ID
<20090510033659.GC7193@cordes.ca>
 If a cherry-pick requires conflict resolution, gitk does:
if {[confirm_popup [mc "Cherry-pick failed because of merge\
                        conflict.\nDo you wish to run git citool to\
                        resolve it?"]]} {
 That gives the user a Yes/Cancel dialog, but in this case Cancel
really means "No, don't run anything", _not_ cancel the cherry-pick.
So IMHO, it would be better if the dialog options were Yes/No.
 If you added the button text as parameters to the confirm_popup
function, you'd have to pass it the default strings everywhere, and
the extra visual noise of all that would probably make this bug not
worth fixing.
 Unless tcl supports functions with default arguments, like C++'s
int foo(int i, int j=42);  Unfortunately I don't know tcl.
 git (with gitk and git gui) is the best thing since emacs.  Happy
hacking!
-- 
#define X(x,y) x##y
Peter Cordes ;  e-mail: X(peter@cor , des.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BC
Message 1 of 1 in “cosmetic bug in gitk cherry-pick”
  1. Peter CordesMay 10, 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.