{"thread":{"id":"3199","subject":"Third newbie question: gitk --all refresh?","startedAt":"2006-01-31T16:46:48Z","lastAt":"2006-01-31T16:46:48Z","messageCount":1,"participants":["Romano Giannetti"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"15303","messageId":"20060131164648.GA1859@pern.dea.icai.upcomillas.es","threadId":"3199","inReplyTo":null,"subject":"Third newbie question: gitk --all refresh?","fromName":"Romano Giannetti","fromEmail":"romanol@upcomillas.es","sentAt":"2006-01-31T16:46:48Z","receivedAt":"2006-01-31T16:46:48Z","isPatch":false,"sender":{"key":"romanol@upcomillas.es","avatar":null},"body":"I have a little problem: is gitk supposed to be possibly run in background\nand then refresh when told? It seems to me that it can track only some\nchanges...  Better let git (1.0.8) speak: \n\npern:~/% mkdir gitk_r\npern:~/% cd gitk_r\npern:~/gitk_r% git init-db\ndefaulting to local storage area\npern:~/gitk_r% echo \"one\" > one.txt\npern:~/gitk_r% echo \"two\" > two.txt\npern:~/gitk_r% git add .\npern:~/gitk_r% git commit -a -m \"commit 1\"\nCommitting initial tree efa4c546776cd5539cb54969a5e1c110b3232ee2\npern:~/gitk_r% git branch\n* master\npern:~/gitk_r% git checkout -b second master\npern:~/gitk_r% git branch\n  master\n* second\npern:~/gitk_r% echo \"three\" > three.txt\npern:~/gitk_r% git add three.txt\npern:~/gitk_r% ls\none.txt  three.txt  two.txt\npern:~/gitk_r% git commit -a -m \"commit second\"\npern:~/gitk_r% echo \"one one\" >> one.txt\npern:~/gitk_r% git commit -a -m \"commit on second #2\"\npern:~/gitk_r% git checkout master\npern:~/gitk_r% echo \"two two\" >> two.txt\npern:~/gitk_r% gitk --all &\n[1] 787\npern:~/gitk_r% : Now git is showing ok\npern:~/gitk_r% git pull . second\nTrying really trivial in-index merge...\nWonderful.\nIn-index merge\n one.txt   |    1 +\n three.txt |    1 +\n 2 files changed, 2 insertions(+), 0 deletions(-)\n create mode 100644 three.txt\npern:~/gitk_r% : Now gitk refreshes ok\n\nWhat I mean if that I select update - reread references it's all ok, I see\nthe merge. \n\npern:~/gitk_r% git branch -d second\nDeleted branch second.\npern:~/gitk_r% : Now gitk did not delete the second branch\n\nWhat I mean that I can do the same update - reread references but \"second\"\nbranch stay there...\n\npern:~/gitk_r% : but\npern:~/gitk_r% gitk --all\npern:~/gitk_r% : this is ok\n\nThat is, the two instances of gitk --all are showing different things: the\n\"old\" running one continue to show the old \"second\" branch in green.\n\nIs this supposed to be like that? Or is \"driver\" (aka /me) error?\n\n   Romano\n\n-- \nRomano Giannetti             -  Univ. Pontificia Comillas (Madrid, Spain)\nElectronic Engineer - phone +34 915 422 800 ext 2416  fax +34 915 596 569\nhttp://www.dea.icai.upcomillas.es/romano/\n"}]}