R P Herrold wrote: >>Do you have the emacs-git package installed? And do you use the >>emacs git integration? That's the part that needs some love, as >>upstream git now rely's on the files shipped as part of emacs >= >>22.2. > > nope -- using one operating iscomplex enough for me ;)
Haha, I completely understand. >>An emacs user who can help us find and test a good solution is what >>we need. > > * nod * thus my poke to smooge, as to some testing I did notice since I posted the other day that it's not git-init.el that's different between us and RPMForge. The trouble is in the lack of a vc-git.el script in newer upstream releases. The RPM Forge packages don't do anything about this, so I would presume that they either haven't noticed the change or don't care enough about emacs support to let it hold up a nice git update (which I can understand). If there are as many emacs-git users of the RPM Forge packages as there are of the EPEL packages, I can see how simply dropping that functionality could easily go unnoticed. :) -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Whenever I feel blue, I start breathing again.
pgpUqrc4S62Sw.pgp
Description: PGP signature
_______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
