Pre-commit review from git patch separates changes into two trees

[Gary Gary]

Hi

I have created a git patch file

git diff - -U999999  TARGET_BRANCH > my.patch

and uploaded it to create a pre-commit review.

This reults in a review with two trees. New/modified files are displayed under tree "a" and new files are displayed under tree "b". I guess this is related to gits use of "A" to represent the file pre-change and "b" to reflect the file post-change. This distinction has not relevance in the context of a Crucible review.

Do I need to create my patch ion a different way to prevent this from happening?

Thanks

[Sergey Svishchev]

Could you post a sample of your patch file?