On 2 June 2013, Marc Weber <[email protected]> wrote:
> I've been thinking about what's causing trouble to me.
> Lack of workflows - lack of documentation.
>
> http://vim.sourceforge.net/ -> download -> patch
> No hint about how patches should be submitted.
> No hinting about release cycles
> NO hinting about how to manage vim source and patches.
>
> I'm used to git.
[...]
> Summary: Almost all problems would be gone by providing an official
> github based mirror using git. Patches which are ready could still be
> applied to mercurial.
>
> I know there are many mercurial users on this list, please helsp my
> mind change, and tell me how the I can setup a mercurial based
> workflow which doesn't get into my way - which is as easy as the git
> based is I described above.
[...]
> People like ZyX should not spend their time on repating lists of
> patches which should be included. Such behaviour might be a sign of
> lack of infrastructure - and that infrastructure is there, we just
> have to use it.
[...]
Are you trying to solve your own problem, or (your perception of)
somebody else's problem? If the former, may I suggest the following
workflow:
(1) Get this file, bridging Mercurial to Git:
https://github.com/felipec/git/blob/fc/master/contrib/remote-helpers/git-remote-hg.py
Rename it git-remote-hg, make it executable, and copy it to your
$PATH; see also:
http://felipec.wordpress.com/2012/11/13/git-remote-hg-bzr-2/
(2) Clone the sources, then go make some coffee:
git clone hg::https://vim.googlecode.com/hg/ vim
(3) Create a branch for each feature you're working on, then patch,
test, push to GitHub, whatever;
(4) Update master, then rebase your branches, or merge master to them;
(5) When you have something to show, run
git diff -r master
and post the output to the list.
Would that work for you?
/lcd
--
--
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/groups/opt_out.
