Re: Organizing package.el a bit

[Artur Malabarba <bruce.connor.am@gmail.com>]

I just pushed a proposal for this (using page-breaks, not separate
files) into scratch/organizing-package.el, but if people don't want me
to do the reorganization, I'll just delete the branch and forget about
it.

The branch is just a bunch of moving around. The only code change is
on the first commit, it moves `package-version-join' to subr.el (with
the other version-* functions) under the name `version-join'.

Oddly, it's causing the test `file-notify-test03-autorevert-remote' to fail.

2015-03-29 10:04 GMT+01:00 Steinar Bang <sb@dod.no>:
>>>>>> Artur Malabarba <bruce.connor.am@gmail.com>:
>
>> I'd like to know whether it's ok to split it into two files,
>> package.el and package-menu.el?
>
>> The distinction is very logic, there's a ton of stuff that goes on in
>> package.el which doesn't make any use of the package-menu.
>> The only downside of this refactoring would be to mess up things like
>> `git-blame`, and that's why I'm askinghere.
>
> If you do
>  cp package.el package-menu.el
>  git add package-menu.el
>  git commit -m "Copying verbatim to preserve history"
>
> before you start working, and then do your changes by removing stuff
> from package-menu.el (and package.el) and not move things around
> otherwise, then git-blame should show the correct history.
>
>