Same as Issue #20439 except for the contributions repository, instead of the core repository.

From 20439:

"There's no easy way for a site administrator to tell which version of Drupal software his site is running. This is particularly a problem when an administrator manages multiple sites at multiple hosts. The problem becomes even more exacerbated when the same admin only has limited time to update the software on sites, resulting in confusion as to just what version is running where.

While there are a lot of technical solutions to this problem, some of which I'd like to implement, this patch is the simplest and least invasive. It simply adds the CVS release tag name to each file which can take such a tag. An admin can thus look in any file and see which release it is."

This patch is for all repository files which contain the CVS $Id$ keyword.

CommentFileSizeAuthor
releasename_contrib.patch676.07 KBChris Johnson

Comments

Bèr Kessels’s picture

Bèr Kessels commented
Status: Needs review » Needs work

Makes sense, but I dislike the idea of applying this patch to al contributions. They wil /all/ be updated.

Besides, this obviously does no longer apply :p

Chris Johnson’s picture

Chris Johnson commented

Am I correct in guessing you (Bèr) don't like this applying to *all* contrib because some are very old and applying this will make them look like they were updated recently? Or is there another reason?

bdragon’s picture

bdragon commented
Version: x.y.z » 5.x-dev
Status: Needs work » Closed (fixed)

Drupal 5 has the facilities for modules to report their version.
Also, the patch is out of date ;)

Hopefully the changes for Drupal 5 will be good enough. (also, touching every file with an $Id$ tag isn't exactly "the least invasive" solution imho)

Closing, mumble