Getting the deps for a single commit is overly complicated

[mstefani]

I have been using until now git-deps 0.1.0-15-gbd9ed69.
With that git deps commit would get the dependencies just for commit.

That changed with

commit d601e35f6ea42eb6110e3d1449d03f16a1da3f10
Author: Adam Spiers <[email protected]>
Date:   Thu May 26 00:28:25 2016 +0100

    allow passing a revision range to CLI or web UI

With that git deps commit gets now the dependencies for commit and all older commits.
To get now the deps just for commit one has to use the unwieldy:
git deps commit^..commit

[aspiers]

Yes, it does expect a range now. It's worth noting that you can type

git deps commit^!

which is shorter than

git deps commit^..commit

Having said that, there is a proposal in #67 for making this more user-friendly, but I haven't got around to figuring out how to finish it yet.

[midenok]

What --recurse option means then? I guess if single commit specified it should work like for single commit, not for -Infinity..commit. Duplicates #90.

[aspiers]

@midenok commented on April 18, 2019 12:30 PM:

What --recurse option means then? I guess if single commit specified it should work like for single commit, not for -Infinity..commit. Duplicates #90.

--recurse is different, because then it recurses through discovered dependencies rather than only analysing the commits mentioned on the CLI.