GNU bug report logs -
#58196
27.0.50; ediprolog 2.2: Please upload the new version to ELPA
Previous Next
Full log
Message #52 received at 58196 <at> debbugs.gnu.org (full text, mbox):
> It will make 2 changes:
>
> - Change copyright line to make it compatible with GNU ELPA requirements.
> - Add a `Version: 2.2` header line so GNU ELPA can make a release of the
> new code.
> - Tell Git that those changes have been merged, so it can properly track
> future changes from your repository.
I added a hack in GNU ELPA's scripts to deal with the third point, but
the other two are still a problem:
- As long as you use another copyright line, every time you make a change
to that line, the automatic merge will fail because of a merge
conflict, so it will require manual intervention.
- As long as you don't use the `Version:` header, the scripts won't know
when you want to make a new release, so again manual intervention will
be needed every time you want to make a release.
Could you please please pretty please help me reduce my workload by
avoiding those needs for human intervention?
The best way you can do that is:
cd .../where/you/keep/your/clone/of/ediprolog/
git fetch git://git.sv.gnu.org/emacs/elpa.git scratch/ediprolog
git merge FETCH_HEAD
-- Stefan
This bug report was last modified 123 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.