[
https://issues.apache.org/jira/browse/YETUS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758751#comment-16758751
]
Allen Wittenauer commented on YETUS-788:
----------------------------------------
-00:
* adds a three new options to smart-apply-patch:
{code}
--changedfilesreport=<name> List of files that this patch modifies
--changedmodulesreport=<name> List of modules that this patch modifies
--changedunionreport=<name> Union of modules that this patch modifies
{code}
Some special notes about the modules report:
* If the patch introduces new modules, they will only be picked up AFTER
committing. So in --dry-run mode, only EXISTING modules are found
* module reordering is NOT supported. So this will not reflect test-patch's
test order.
> expose patch analysis
> ---------------------
>
> Key: YETUS-788
> URL: https://issues.apache.org/jira/browse/YETUS-788
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.9.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Attachments: YETUS-788.00.patch
>
>
> Expose precommit's patch analysis so that decisions can be made based upon
> what a patch touches. For example, if a change hits a certain set of
> directories or hits a certain module, some pre-work may be required prior to
> running test-patch.
> Since Yetus already has the logic to do the hard work, this should just be a
> matter of exposing the results of that work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
