Markus Heidelberg wrote:
> For me, a proper project history from developer view is equal to good
> documentation from user view.
It's been some since we looked at this, and the information is now
scattered over several messages.
Markus, could you make the step-by-step description of what needs to be
done? I need exact steps and some hints about what to do when there are
errors.
I do intend to use the "export to github" feature of the Google code
site, so that (hopefully) issues will be deep-linked to their new place.
I do assume that after the Mercurial repository is converted to git, we
could just wipe it out and replace it with another.
I would rather not take the risk of messing up the Mercurial repository.
Thus would the best approach be to do the conversion locally and replace
the git repository on github? We could even try that out now, since the
github repository is for testing anyway.
--
CUSTOMER: You're not fooling anyone y'know. Look, isn't there something
you can do?
DEAD PERSON: I feel happy... I feel happy.
[whop]
CUSTOMER: Ah, thanks very much.
MORTICIAN: Not at all. See you on Thursday.
CUSTOMER: Right.
The Quest for the Holy Grail (Monty Python)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
