infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18554) Github mails don't always include change diffs
Date Sun, 02 Jun 2019 20:20:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854102#comment-16854102
] 

Sebb commented on INFRA-18554:
------------------------------

Sorry, bad example.

How about the commits which are noted here:
https://lists.apache.org/thread.html/72042c11cb97a335cbdb48a430d751b798fe6c43465dd47851ec770c@%3Ccommits.whimsical.apache.org%3E
I cannot find diffs for:
new 83d78d7  Fix typo
new 503d4e7 Use sks-keyservers.net instead of pgp.mit.edu

> Github mails don't always include change diffs
> ----------------------------------------------
>
>                 Key: INFRA-18554
>                 URL: https://issues.apache.org/jira/browse/INFRA-18554
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Github
>            Reporter: Sebb
>            Assignee: Daniel Gruno
>            Priority: Major
>
> Changes to ASF repos made via GitHub don't always show the commit diff.
> For example, the following commit [1]  on May 30th should appear as a diff on commits@logging.a.o.
However it does not appear to be there [2].
> This makes it impossible to perform CTR from the mailing list as is the case for SVN
updates.
> If the code cannot be fixed to show the diffs in the emails, then perhaps at least the
email could be amended to include links to the changes so the reader can review changes without
needing to trawl the Git repo.
> [1] https://github.com/apache/logging-log4j-audit/commit/b4da24faa2e7a498ec690009c606ae3234342148
> [2] https://lists.apache.org/list.html?commits@logging.apache.org:dfr=2019-05-30|dto=2019-05-31



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message