Comment #6 on issue 2494 by elliot.w...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
guys this is a big deal. merge conflicts exist, and their resolutions
involve actual code that needs peer review ju
Updates:
Labels: Component-SCMTools
Comment #5 on issue 2494 by trowb...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
(No comment was entered for this change.)
--
You received this message beca
Updates:
Status: New
Comment #4 on issue 2494 by trowb...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
(No comment was entered for this change.)
--
You received this message because you are sub
Comment #3 on issue 2494 by elliot.w...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
e.g.:
wolke:~$ mkdir /tmp/a; cd /tmp/a
wolke:/tmp/a$ git init
Initialized empty Git repository in /tmp/a/.git/
wolke:
Comment #2 on issue 2494 by elliot.w...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
merge conflict resolution.
--
You received this message because you are subscribed to the Google Groups
"reviewboar
Updates:
Status: NeedInfo
Comment #1 on issue 2494 by trowb...@gmail.com: manually uploaded git
diff-tree --cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
I can't seem to produce a diff with any content given the instructions you
provided.
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2494 by elliot.w...@gmail.com: manually uploaded git diff-tree
--cc produce 'diff file is empty'
http://code.google.com/p/reviewboard/issues/detail?id=2494
What version are you running?
bleeding edge, c848031b769cf84b8f9fe4