It looks like the consensus on Fields-related modules is to use the plural in the package name—Fields rather than Field. Patch to follow.

CommentFileSizeAuthor
#3 markup-1404442-3.patch635 bytestraviscarden
#1 markup-1404442-1.patch646 bytestraviscarden

Comments

traviscarden’s picture

traviscarden commented
Assigned: traviscarden » Unassigned
Status: Active » Needs review
StatusFileSize
new markup-1404442-1.patch646 bytes
interx’s picture

interx commented

Yep, it should be under Fields.

Also, the line 

files[]=markup.module

should be removed.

traviscarden’s picture

traviscarden commented
Title: Change package from Field to Fields (plural) » Fix up markup.info
StatusFileSize
new markup-1404442-3.patch635 bytes

All right. Here's an updated patch that...

  • Removes the CVS $Id tag,
  • Changes the package name to "Fields", and
  • Removes the superfluous files[] declaration, along with the version, which the packaging system will add.
adellefrank’s picture

adellefrank commented
Status: Needs review » Reviewed & tested by the community

Works as advertised, thanks, TravisCarden!

adellefrank’s picture

adellefrank commented
Status: Reviewed & tested by the community » Patch (to be ported)

Let's get this beautiful, simple bit of organization into this super-helpful module, eh? :)

traviscarden’s picture

traviscarden commented
Status: Patch (to be ported) » Reviewed & tested by the community

@adellefrank: I think "reviewed & tested by the community" is what you meant. "patch (to be ported)" is for when the patch has already been committed to one version of the project and needs to be ported to another version. See Status settings for an issue. Thanks for reviewing. Sometimes it takes a master of Library Science to get a complicated organizational change like this approved. ;-)

bcostlow’s picture

bcostlow commented
Status: Reviewed & tested by the community » Closed (fixed)

Added the the latest 7.x release.