Aaron> When this is done, I will import the parts of Classpath that do
Aaron> not overlap with gjc. Ditto for the other way around.
I recommend simply copying the existing Classpath ,v files to
subversions. This will preserve history. Then we can address the
merge as an operation which simply extends the existing history.
Paul was talking about doing the merge work on a branch (of
Classpath).
Aaron> 2. Classpath currently doesn't use ChangeLog entries, gjc does I
Aaron> believe. (Classpath was supposedly going to auto-generate a change
Aaron> log based on CVS commits, but I never saw this happen in practice).
Aaron> Should we switch to the Cygnus approach?
The gcj project requires ChangeLog entries.
We prefer one ChangeLog file at the top of the tree. This makes it
easy to understand how changes are being made, and by whom.
Aaron> 3. The current Classpath archive sends CVS commit messages to
Aaron> [EMAIL PROTECTED], which is basically just a mail alias
Aaron> on the GNU server, not a real mailing list. Should we set this up
Aaron> as a real smartlist list and allow people to subscribe to it?
Yes, absolutely.
Tom