[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA update
From: |
Stephen J. Turnbull |
Subject: |
Re: ELPA update |
Date: |
Thu, 29 Sep 2011 10:16:10 +0900 |
PJ Weisberg writes:
> You could set up your cron job to publish new versions only of
> packages that have had their version number changed. Updating the
> version number could be analogous to "tagging" a release in a normal
> one-project repository.
That's a little constraining. I don't do it for any personal projects
since I started using git, but I used to bump versions every time I
got a new working version. In a multi-developer project, that kind of
custom might be harder to terminate.
How about triggering based on a tag name convention, like "a tag of
the form 'release-FOO-N-NN' means to update the downloadable package"?
- Re: ELPA update, (continued)
- Re: ELPA update, Ted Zlatanov, 2011/09/28
- Re: ELPA update, Julien Danjou, 2011/09/28
- Re: ELPA update, Ted Zlatanov, 2011/09/28
- Re: ELPA update, Julien Danjou, 2011/09/28
- Re: ELPA update, Ted Zlatanov, 2011/09/28
- Re: ELPA update, Stefan Monnier, 2011/09/28
- Re: ELPA update, PJ Weisberg, 2011/09/28
- Re: ELPA update,
Stephen J. Turnbull <=
- Re: ELPA update, Ted Zlatanov, 2011/09/29
- Re: ELPA update, Julien Danjou, 2011/09/29
- Re: ELPA update, Ted Zlatanov, 2011/09/29
- Re: ELPA update, Julien Danjou, 2011/09/29
- Re: ELPA update, Ted Zlatanov, 2011/09/29
- Re: ELPA update, Stephen J. Turnbull, 2011/09/29
- Re: ELPA update, Eli Zaretskii, 2011/09/28
Re: ELPA update, Jambunathan K, 2011/09/29