>>>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:

 >> ISTR that the importing of a new package as a GNU ELPA Git branch
 >> was earlier referred to as “tricky”; is there any guide on that I
 >> could use?

 > Either use "git subtree add ..." in the master branch of elpa.git or
 > push it as a new branch named `externals/<pkg>' in elpa.git.  Then
 > adjust the `externals-list' file in the master branch of elpa.git.

	IOW, with the patch MIMEd?

 >> As for the reason, I guess I now have one: as new versions are
 >> packaged as soon as the Version: header changes in the tree, I guess
 >> I’d rather rewrite my Git history to accommodate for that.

 > The package-release machinery doesn't really pay attention to the
 > metadata, so if the HEAD has a "Version: 0" no package will be
 > produced, even if earlier revisions had "Version: <foo>".  So it
 > doesn't require any history rewriting.

	… Not to mention that there was no mw.el file to begin with.

	Nevertheless, I’ve fixed a somewhat inaccurate wording in one of
	the commit messages; combined the “version bump” change with the
	addition of copyright notice to README and the “yearly update”
	of the already present copyright notices; and get rid of a
	misleading README change (which, among other things, documented
	a change in behavior not yet actually made at that time.)

	Now I’ve found some flaws in the topmost commit on the new
	exp-x54e65706 branch, and intend to amend it shortly…

[…]

-- 
FSF associate member #7257  np. Eyes of Fire — Rainbow  … 3013 B6A0 230E 334A