[PATCH 2/2] git-rev-list.txt: Clarify the use of multiple revision arguments
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Aug 5, 2009, 07:58 UTC
- Message-ID
- <1249459117-3853-2-git-send-email-git@drmicha.warpmail.net>
- In-Reply-To
- <1249459117-3853-1-git-send-email-git@drmicha.warpmail.net>
If one thinks of a revision as the set of commits which can be reached from the rev, and of ^rev as the complement, then multiple arguments to git rev-list can be neither understood as the intersection nor the union of the individual sets.
But set language is the natural as well as logical language in which to phrase this. So, add a paragraph which explains multiple arguments using set language.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> --- While one could explain this also by describing the revision walker, I think that and/or/union/intersection should be clearer for the average user.
We may even want to add a paragraph which explains how one gets "A intersected B", which is impossible to do with rev-list.
Documentation/git-rev-list.txt | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt index 847cc7d..40ca276 100644 --- a/Documentation/git-rev-list.txt +++ b/Documentation/git-rev-list.txt @@ -66,6 +66,13 @@ command: means "list all the commits which are included in 'foo' or 'bar', but not in 'baz'". +So, the resulting set of commits is the union of 'foo' and 'bar', +intersected with the complement of baz. The order of arguments is +irrelevant: first, the union of all positive refs (those without +'{caret}') is taken, then the result is intersected with all negative +refs (i.e. with the complement of the union of all refs which appear +with a preceding '{caret}'). + A special notation "'<commit1>'..'<commit2>'" can be used as a short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of the following may be used interchangeably:
-- 1.6.4.70.g9c084