infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15974) ASF github messages don't appear to have In-Reply-To headers
Date Fri, 01 Mar 2019 04:35:00 GMT

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

Chris Lambertus commented on INFRA-15974:
-----------------------------------------

[~humbedooh] is what Sebb's asking even possible for case #2? I'll be honest, this seems like
nitpicking, and I'm not inclined to suggest we expend any infra resources on it. The foundation's
goal of capturing the commit has been met, and that is sufficient.


> ASF github messages don't appear to have In-Reply-To headers
> ------------------------------------------------------------
>
>                 Key: INFRA-15974
>                 URL: https://issues.apache.org/jira/browse/INFRA-15974
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Minor
>
> It looks like the messages generated by the ASF Github service don't have the In-Reference-To
(correction, that should be In-Reply-To) header set for replies and comments.
> This makes it hard to follow threads.
> For example, pr 739 is opened [1] and closed [2] but there is no link between the two.
> [1] https://lists.apache.org/api/source.lua/983746bdd657fd029322cce85abd5b240114e3b6c4764385ffefb0de@%3Ccommits.infra.apache.org%3E
> [2] https://lists.apache.org/api/source.lua/90328c800b1b287dd8154404d9accbdb51557c7c85709e440041f1aa@%3Ccommits.infra.apache.org%3E



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

Mime
View raw message