[
https://issues.apache.org/jira/browse/YETUS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556105#comment-16556105
]
David Smiley commented on YETUS-645:
------------------------------------
See SOLR-12561 which has 3 patches. First one is a plain IntelliJ patch file,
the second two were processed through that script. In this case, Yetus
probably didn't have enough time to process the first patch since I quickly
uploaded a new one when I realized it wasn't going to like the first.
[~steve_rowe] commented in LUCENE-8369 that he thought the problem there was my
IntelliJ created patch. Maybe? Yetus did post a comment at least.
> Make leading path component optional in patch files (support IntelliJ patch
> files)
> ----------------------------------------------------------------------------------
>
> Key: YETUS-645
> URL: https://issues.apache.org/jira/browse/YETUS-645
> Project: Yetus
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Major
>
> IntelliJ IDEA has a "create patch" feature that generates patch files in a
> format that isn't supported by some tools like Yetus. In particular, there
> is no leading "a/" and "b/" in the paths. That appears to be the sole
> difference requiring these patches to be supported.
>
> See [https://youtrack.jetbrains.com/issue/IDEA-92793]
>
> To work around this, I wrote a one-liner Bash script using SED to insert the
> "a/" and b/" at the right spots:
> {code:java}
> sed -i '' -e 's/^--- /--- a\//g' -e 's/^+++ /+++ b\//g' "$1"
> {code}
> In this issue I propose that Yetus detect the absence of a/ and b/ and either
> (a) insert them using a similar script, or (b) toggling the "-p" option when
> the patch is applied using [git-apply|https://git-scm.com/docs/git-apply] or
> other tool.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
