{"thread":{"id":"20026","subject":"Verbose output of git commands","startedAt":"2009-07-05T10:58:56Z","lastAt":"2009-07-05T14:06:33Z","messageCount":2,"participants":["Daniel Trstenjak","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"117455","messageId":"20090705105856.GC5689@laptop","threadId":"20026","inReplyTo":null,"subject":"Verbose output of git commands","fromName":"Daniel Trstenjak","fromEmail":"daniel.trstenjak@online.de","sentAt":"2009-07-05T10:58:56Z","receivedAt":"2009-07-05T10:58:56Z","isPatch":false,"sender":{"key":"daniel.trstenjak@gmail.com","avatar":null},"body":"\nHi all,\n\nwhen starting with git it's very nice to have all this helpful hints in\nthe output of the git commands. But know, after I can handle git quite well,\nall this helpful hints hinder me to get the core information of the\ncommands. \n\nE.g:\ngit status\n\nfile: needs merge\n# Not currently on any branch.\n# Changed but not updated:\n#   (use \"git add <file>...\" to update what will be committed)\n#   (use \"git checkout -- <file>...\" to discard changes in working directory)\n#\n#       unmerged:   file\n#\n# Untracked files:\n#   (use \"git add <file>...\" to include in what will be committed)\n#\n#       init\n\n\nThe core information is just:\n\nunmerged : file\nuntracked: init\n\n\n\nIt would be nice to be able to configure an expert mode, in which only\nthe core information of the git commands is printed out.\n\nJust some thoughts.\n\n\n\nGreetings,\nDaniel\n"},{"id":"117457","messageId":"vpqocrz5imu.fsf@bauges.imag.fr","threadId":"20026","inReplyTo":"20090705105856.GC5689@laptop","subject":"Re: Verbose output of git commands","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2009-07-05T14:06:33Z","receivedAt":"2009-07-05T14:06:33Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Daniel Trstenjak <Daniel.Trstenjak@online.de> writes:\n\n> E.g:\n> git status\n>\n> file: needs merge\n> # Not currently on any branch.\n> # Changed but not updated:\n> #   (use \"git add <file>...\" to update what will be committed)\n> #   (use \"git checkout -- <file>...\" to discard changes in working directory)\n> #\n> #       unmerged:   file\n> #\n> # Untracked files:\n> #   (use \"git add <file>...\" to include in what will be committed)\n> #\n> #       init\n>\n>\n> The core information is just:\n>\n> unmerged : file\n> untracked: init\n\nThe\n\n# Not currently on any branch.\n\nalso contains some relevant information.\n\n> It would be nice to be able to configure an expert mode, in which only\n> the core information of the git commands is printed out.\n\nAgreed, but even without that, I find 'ui.color = true' to solve most\nof the issue: the relevant text is shown colored, and the color tells\nme whether the change is staged or not. So, I can still concentrate on\nthe important.\n\nOther than that, \"git diff --name-status\" can help, too.\n\n-- \nMatthieu\n"}]}