sourcetree full revision in patch

When I generate a patch in sourcetree, it doesn't look like it's putting the full revision in the patch. For example, from SourceTree I'll get:

index 19e3ab7..f21414a 100644

But when getting the patch from the command line, I'll get:

index 19e3ab72e04ce4f4f34c45f6f4135ab7904c3441..f21414a48b7105eaec5e8c1570daa47083a6e947 100644

How can I get the full value from SourceTree's patch?

4 answers

0 votes

Same problem here with ReviewBoard. +1 for full revisions.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

0 votes

+1 for the full revision option. The patch generated can not be used in ReviewBoar. It made me generate diff file in cmd-line.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

0 votes

Is there a reason that SourceTree's shorthand is insufficient?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

0 votes

We use ReviewBoard to code review, and it doesn't like the shorthand:

The revision '19e3ab7' for 'file.php' isn't in a valid format: The SHA1 is too short. Make sure the diff is generated with `git diff --full-index`.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.