[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1974 Thanks @rhtyd! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1974 @dmabry yes you may close this, I'll cherry pick this on 4.9 from the merged commit on master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1974 shall I close this PR or do you guys need it open to make sure the cherry-pick happens? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1974 LGTM, looks like we'll have to backport by cherry-picking this given the PR for master has been merged. Thanks @dmabry --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1974 Done. I'll also do a cherry pick on the other PR. Thanks for the guidance @rafaelweingartner. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1974 @rafaelweingartner No problem. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ...
Github user rafaelweingartner commented on the issue: https://github.com/apache/cloudstack/pull/1974 @dmabry what about using `git cherry-pick` to introduce the changes that were already merged into master in 4.9? Then, we can maintain the same commit hash. This would facilitate tracking quite a lot. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
