{"thread":{"id":"39904","subject":"[BUG] gitk deals badly with --not","startedAt":"2015-07-21T09:38:37Z","lastAt":"2015-07-21T09:38:37Z","messageCount":1,"participants":["ydirson@free.fr"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"266534","messageId":"1545730766.15139362.1437471517806.JavaMail.root@zimbra39-e7.priv.proxad.net","threadId":"39904","inReplyTo":"1236236440.15093493.1437470465599.JavaMail.root@zimbra39-e7.priv.proxad.net","subject":"[BUG] gitk deals badly with --not","fromName":"","fromEmail":"ydirson@free.fr","sentAt":"2015-07-21T09:38:37Z","receivedAt":"2015-07-21T09:38:37Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"When gitk is run with \"<some refs> --not <some other refs>\" args, things work fine until one tries to modify the view.\nThere it considers \"--not\" to be an extra git-log argument on its own, and groups the negative refs together with the\npositive refs, which naturally gives completely wrong results.\n\nNot sure what the best course of action would be to fix that:\n* add negative refs the extra args could be an option, since those are added last to the commandline, but then the\n  \"edit\" dialog becomes a bit strange, with refs listed at both ends of it\n* add a dedicated field for negative refs\n* convert them to the ^ref syntax\n\nEither of those last 2 solution raise the concern of convertion between ^ and --not: in the case where we add a dedicated\nfield, would there be any reason not to move ^refs to this field instead ?\n"}]}