Re: [PATCH 3/5] revision.c: get rid of struct rev_info.prune_data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nguyán ThÃi Ngác Duy  <pclouds@xxxxxxxxx> writes:

> There are three struct pathspec(s) in struct rev_info:
>
>  - prune_data
>  - pruning.pathspec
>  - diffopt.pathspec
>
> In some places, this pathspec is used, in other places another
> ... but i'm
> not sure why diffopt can't be used in place of pruning.

A command in the "log" family uses revision traversal and uses one
pathspec (pruning.pathspec) to cull side branches and skip irrelevant
commits, and another pathspec (diffopt.pathspec) to specify how the found
commit is shown.  Off the top of my head, currently the only case the
pathspec of these diff options differ is when --full-diff is used, but
they are independent concepts.

I would suspect this would matter even more once somebody wants to redo
the --follow hack to actually follow different renamed-from path per
merged branches, but I haven't thought through the issues.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]