You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sergio Fernández (JIRA)" <ji...@apache.org> on 2013/08/27 16:52:52 UTC

[jira] [Updated] (INFRA-6697) Right temporal order of git commit messages on Jira

     [ https://issues.apache.org/jira/browse/INFRA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Fernández updated INFRA-6697:
------------------------------------

    Description: 
I realized that the jira-bot pushes the commit messages in reverse order (the oldest come the last). This is not so important, but when you push several commits it's a bit difficult to follow the thread from jira.

I don't know how this is implemented, but probably piping the output of 'git log', so options such as --topo-order or --date-order could help.

  was:
I realized that the jira-bot pushes the commit messages in reverse order (the oldest come the last). This is not so important, but when you push several commits it's abit difficult to follow the thread from jira.

I don't know how this is implemented, but probably piping the output og 'git log', so options such as --topo-order or --date-order could help.

    
> Right temporal order of git commit messages on Jira
> ---------------------------------------------------
>
>                 Key: INFRA-6697
>                 URL: https://issues.apache.org/jira/browse/INFRA-6697
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git, JIRA
>            Reporter: Sergio Fernández
>            Priority: Minor
>
> I realized that the jira-bot pushes the commit messages in reverse order (the oldest come the last). This is not so important, but when you push several commits it's a bit difficult to follow the thread from jira.
> I don't know how this is implemented, but probably piping the output of 'git log', so options such as --topo-order or --date-order could help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira