Port to Drupal 6

I needed this for my site upgrade. Simple patch really. I am still getting one notice though when creating new content:

notice: Undefined property: stdClass::$nid in /Users/addi/Sites/6drupal/sites/all/modules/ed_readmore/ed_readmore.module on line 78.

I'll circle back and get a look at it when I have more time but in the meantime, it works.

Note that the patch is against the 5 branch since HEAD is not complete.

It didn't update the .info file correctly, I changed ed_readmore.info manually until you update the patch with these values and removed the rest:
name = "Read More Tweak"
description = "Customize the 'read more' link shown in drupal teasers."
core = 6.x
project = "ed_readmore"
datestamp = "1198354808"

You .info stuff is incorrect. Everything that appears below "; Information added by drupal.org packaging script on 2007-04-06" in the tarball should not be in the .info file in CVS - it is added by the packaging script. You tried to patch against a tarball which already had this info added to it. If you patch against CVS you will see it works fine.

I have no idea where you get datestamp, but that definitely should not be in the info file - if it is there at all that would be something, again, added by the packager.

This page (http://drupal.org/node/101009) explains .info files. It is for D5 but they are essentially the same in D6 except the addition of the "core" field.

The only thing that is wrong is the project line that should normally get set by the module install script automatically, so that's true.

But datestamp and the rest is valid line for manual normal editing.
Datestamp = http://drupal.org/node/149280

Also, not only core is new for Drupal 6 .info file, also old dependencies has changed to dependencies[] array.

Yes, I know there are other changes (like php version, for example.) I just meant significant ones for this module, i.e. new lines to add.

Re: datestamp, yes it is "valid" but not something you should manually add to a module:
"It will be added for "update_status" module by build system" means that it is added by packaging when the tarball is created. How could you possibly know the correct datestamp to put there since it is dependent on the when the packager runs?

Again, anything listed below the "; Information added by drupal.org packaging script on xxxx-xx-xx" should not be manually added to the file in CVS. Those values are determined and added by the packaging script at tarball creation time.

The only reason I added core in manually is for CVS deployment, but we can remove that one too if it bugs you. Re: setting "core" manually:
"Note that the drupal.org packaging script automatically sets this value based on the Drupal core compatibility setting on each release node. So, people downloading packaged themes from drupal.org will always get the right thing. However, for sites that deploy Drupal directly from CVS, it helps if you commit this change to the .info file for you modules."

Any idea when this module is available for Drupal 6? I'm not familiar with handling *.patch files and I'm not sure what CVS means, but I really want the "Read more" link to appear in line with the teaser, and NOT bellow.

When someone can explain me how I apply this patch, then I would be happy. :)

You need to make sure you have the patch command available, which can be gotten in various ways on different OS or through some editor/IDEs (like Eclipse has it built in.) Here is the handbook page on applying pages: http://drupal.org/patch/apply.

Here is Drupal 6 version: http://drupal.org/node/235393