{"thread":{"id":"19618","subject":"inconsistency with --abbrev=0","startedAt":"2009-05-31T15:48:00Z","lastAt":"2009-06-01T10:36:50Z","messageCount":3,"participants":["Markus Heidelberg","Sverre Rabbelier"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"115138","messageId":"200905311748.00782.markus.heidelberg@web.de","threadId":"19618","inReplyTo":null,"subject":"inconsistency with --abbrev=0","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2009-05-31T15:48:00Z","receivedAt":"2009-05-31T15:48:00Z","isPatch":false,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"The minimum (>=4) number of chars is shown by\n\n  git log|show|whatchanged --abbrev-commit --raw --abbrev=0\n  git rev-list --abbrev-commit --abbrev=0 HEAD\n  git show-ref --abbrev=0\n  and the various diff commands\n\nAll 40 are shown by\n\n  git branch -v --abbrev=0\n  git ls-files --stage --abbrev=0\n  git ls-tree --abbrev=0 HEAD\n\nThe latter group uses parse-options and doesn't set abbrev to 4 in this\ncase. This is needed for git-describe to omit the output of the commit.\n\nWhat should --abbrev=0 behave like?\n\nMarkus\n"},{"id":"115156","messageId":"fabb9a1e0905311046t1cd45b2cj4f889313c7781b38@mail.gmail.com","threadId":"19618","inReplyTo":"200905311748.00782.markus.heidelberg@web.de","subject":"Re: inconsistency with --abbrev=0","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-05-31T17:46:31Z","receivedAt":"2009-05-31T17:46:31Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Sun, May 31, 2009 at 17:48, Markus Heidelberg\n<markus.heidelberg@web.de> wrote:\n> What should --abbrev=0 behave like?\n\nIf the minimum is 4, then --abbrev=n with n < 4 should give an error\nsaying that it should be >= 4, no?\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"115190","messageId":"200906011236.51289.markus.heidelberg@web.de","threadId":"19618","inReplyTo":"fabb9a1e0905311046t1cd45b2cj4f889313c7781b38@mail.gmail.com","subject":"Re: inconsistency with --abbrev=0","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2009-06-01T10:36:50Z","receivedAt":"2009-06-01T10:36:50Z","isPatch":false,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"Sverre Rabbelier, 31.05.2009:\n> Heya,\n> \n> On Sun, May 31, 2009 at 17:48, Markus Heidelberg\n> <markus.heidelberg@web.de> wrote:\n> > What should --abbrev=0 behave like?\n> \n> If the minimum is 4, then --abbrev=n with n < 4 should give an error\n> saying that it should be >= 4, no?\n\nThis would break existing workflows. Currently --abbrev=[1-3] (and also\n--abbrev=-n (negative numbers)) always display >=4 chars in all\ncommands. So you don't have to remind git's lower limit of 4, if you\njust want to display as few chars as possible.\nOnly --abbrev=0 is different.\n\nMarkus\n"}]}