Michael Haggerty <mhag...@alum.mit.edu> writes: > That seems very workable.
That is pretty much it. > What is your preference regarding the history to date? The only thing I deeply care about is that initial and subsequent "git pull" I'll do from you [*1*] will pull in commits that touch only the "multimail" part in the contrib/ area and not mixed with unrelated changes to other areas. If the history you have so far would later help others learn the motivation, design, constraints etc. while developing it, which cannot be easily read from the resulting code, i.e. help maintaining it in general, it's a good idea to keep it. In such a case, however, people may want to review that history as well. If it is the "oops, it didn't work, let's try another" kind of "record as we build" type of history that may not help the future maintainace that much, you may instead want to start with a single code-dump "here is the first public version" (which is reviewed in this thread, I think) without the history behind it. Your choice, in other words ;-) [Footnote] *1* This does not even have to be a stable URL I would place in remote.multimail.url configuration; it does not even have to be a non-rewinding tree. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
