cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10013) Migrate to Debian9 systemvmtemplate
Date Wed, 20 Dec 2017 13:12:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10013:

rafaelweingartner commented on issue #2211: CLOUDSTACK-10013: Migrate systemvmtemplate to
   @Daan, @rohit there is no need to squash.
   I like the idea/philosophy of self-contained commits. This means, one commit per issue,
which is normally the case of PRs. This PR, however, is a different case. Frankly speaking,
when I talked about squashing, I only saw the number `23` in the commits tab, but I did not
open it. Looking at the commits I do think that it is good this way. It is my bad that I did
not notice this before.
   What I am against is something that we see sometimes, where people use one commit per file/change.
Then, a single issue that is being tackled in a PR becomes 100+ commits…

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Migrate to Debian9 systemvmtemplate
> -----------------------------------
>                 Key: CLOUDSTACK-10013
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: Future,
> Migrate to debian9 based systemvmtemplate

This message was sent by Atlassian JIRA

View raw message