You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/12 11:25:46 UTC
[jira] [Commented] (CLOUDSTACK-9148) Remove .pydevproject file from
hypervisor-plugin-kvm.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054207#comment-15054207 ]
ASF GitHub Bot commented on CLOUDSTACK-9148:
--------------------------------------------
GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1227
Show actual diff in commits after merge with git-pr / git-fwd-merge
This shows the diff in commits after using `git-pr` and `git-fwd-merge` tools, like this:
```
44e8c92 Merge pull request #1226 from borisroman/CLOUDSTACK-9148
0554610 Removed .pydevproject from plugin kvm hypervisor.
```
That helps in quickly seeing what change is applied and whether it makes sense. It doesn't touch the actual code base. I'm using this patch for some time already.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/remibergsma/cloudstack git-pr-show-commits
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1227.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1227
----
commit 52edbbb6cc2e2c58e360b737143c10adddc43880
Author: Remi Bergsma <gi...@remi.nl>
Date: 2015-12-12T10:00:41Z
Show actual diff in commits after merge
----
> Remove .pydevproject file from hypervisor-plugin-kvm.
> -----------------------------------------------------
>
> Key: CLOUDSTACK-9148
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9148
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Boris Schrijver
> Assignee: Boris Schrijver
>
> It's there for no apparent reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)