commerce_feeds_example .info file

Since 'project' and 'version' is added to info files by d.o they shouldn't be saved to the git repository.

http://drupalcode.org/project/commerce_feeds.git/blob/refs/heads/7.x-1.x...

http://drupal.org/node/542202

version (Discouraged)
    The version string will be added by drupal.org when a release is created and a tarball packaged. However, if your module is not being hosted on the drupal.org infrastructure, you can give your module whatever version string makes sense.

    Users getting their modules directly from git will not have a version string, since the .info files checked into git do not define a version. These users are encouraged to use the git deploy module to provide accurate version strings for the admin/build/modules page for modules in directories checked out directly from git.

    Because Drupal core uses a slightly different packaging process than contributed modules, the core modules have a version line predefined. This is an exception to the rule, not the model for contributed modules.

project (Discouraged, packaging use only)
    Module maintainers should not use this at all. The packaging script on drupal.org will automatically place a string here to identify what project the module came from. This is primarily for the Update status module, so that Drupal installations can monitor versions of installed packages and notify administrators when new versions are available.