Achim Gratz strom...@nexgo.de writes:
Rasmus writes:
Is there any issues with adding a version header to org.el in maint and
master?
I don't think so. It may require to update README_maintainer
accordingly.
Done.
Please revert that change.
Done. I was very busy this week.
Rasmus
--
Rasmus writes:
Done. I was very busy this week.
No worries. Now, if Bastien would make up his mind if we generate an
org.el to facade for the file that will have the content (what will we
name this?)… However, this would have to be done on maint, so there's
the question of whether and when we
Achim Gratz strom...@nexgo.de writes:
Rasmus writes:
Is there any issues with adding a version header to org.el in maint and
master?
I don't think so. It may require to update README_maintainer
accordingly.
Done.
Please revert that change. It's messing with the version numbers on
ELPA
Rasmus writes:
Is there any issues with adding a version header to org.el in maint and
master?
I don't think so. It may require to update README_maintainer
accordingly.
Done.
Please revert that change. It's messing with the version numbers on
ELPA since (as I suspected) the idea of using
Bastien writes:
So there would be two org.el, one bare, non-generated version, with no
Version: header, and another one, generated, with all relevant info?
Of course the non-generated version, being in the same directory, would
need to have a different name. But otherwise, yes.
Regards,
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Since it doesn't appear that there'll be a proper build environment for
ELPA packages anytime soon, the only way out is to generate org.el. We
could do it just for ELPA, although I suggest we go ahead and do it
across the board. We can get
Achim Gratz strom...@nexgo.de writes:
Yes, we don't want to have to commit this nonsense when we have a proper
VCS. Now, instead of simply tagging a release you're back to having to
remember that you have to jump through some burning hoops first in a
particular oder, then commit it and then
Rasmus writes:
I don't really see the issue... Can we add a proper Version headers in
the make process for ELPA packages.
We don't generate org.el; while it would not be impossible to do, I
don't really see why we should just to drop some comment in there.
Besides, it would be perfectly
Hi,
Is there any issues with adding a version header to org.el in maint and
master? Maybe 8.4 or 8.4-dev or 8.4-pre for master...
See:
http://permalink.gmane.org/gmane.emacs.devel/188780
Rasmus
--
Sådan en god dansk lagereddike kan man slet ikke bruge mere
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rasmus ras...@gmx.us writes:
Is there any issues with adding a version header to org.el in maint and
master?
I don't think so. It may require to update README_maintainer
accordingly.
Done.
Maybe 8.4 or 8.4-dev or 8.4-pre for master...
Hello,
Rasmus ras...@gmx.us writes:
Is there any issues with adding a version header to org.el in maint and
master?
I don't think so. It may require to update README_maintainer
accordingly.
Maybe 8.4 or 8.4-dev or 8.4-pre for master...
IMO, 8.4 is fine.
Regards,
--
Nicolas Goaziou
Rasmus writes:
Is there any issues with adding a version header to org.el in maint and
master? Maybe 8.4 or 8.4-dev or 8.4-pre for master...
Yes, we don't want to have to commit this nonsense when we have a proper
VCS. Now, instead of simply tagging a release you're back to having to
remember
12 matches
Mail list logo
