[
https://issues.apache.org/jira/browse/YETUS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067797#comment-16067797
]
Akira Ajisaka edited comment on YETUS-522 at 6/29/17 5:56 AM:
--------------------------------------------------------------
bq. Wont we need to do something similar for github too?
AFAIK, smart-apply-patch already do this for GitHub pull request.
was (Author: ajisakaa):
bq. Wont we need to do something similar for github too?
AFAIK, smart-apply-patch already do this for GitHub.
> smart-apply-patch should do more to infer author in committer mode
> ------------------------------------------------------------------
>
> Key: YETUS-522
> URL: https://issues.apache.org/jira/browse/YETUS-522
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
> Assignee: Akira Ajisaka
> Attachments: YETUS-522.01.patch, YETUS-522.02.patch,
> YETUS-522.03.patch
>
>
> In committer mode, we can guess that the user of smart-apply-patch is
> planning to submit changes. In the case where the patch wasn't made with
> format-patch it would be nice to do some work on behalf of the committer to
> find an author.
> The obvious case is when the patch is associated with a bug system, we can
> get the author from the assignee and set it in a placeholder commit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
