On Do, 27 Aug 2015, Markus Heidelberg wrote:
The git repository doesn't need it and you can't even test the .hgignore
file in the git repository for correct syntax. There might be subtle
differences, I don't know exactly. I think this is best be left to the
HG mirror to convert .gitignore to
On Tuesday, August 25, 2015 at 12:55:29 PM UTC-5, Markus Heidelberg wrote:
Am Dienstag, 25. August 2015, 17:42:26 schrieb Christian Brabandt:
Did the .gitignore file change between the old googlecode repository and
the new github repository? I get a modification here:
diff --git
Am Dienstag, 25. August 2015, 17:42:26 schrieb Christian Brabandt:
Did the .gitignore file change between the old googlecode repository and
the new github repository? I get a modification here:
diff --git a/.gitignore b/.gitignore
--- a/.gitignore
+++ b/.gitignore
@@ -1,5 +1,3 @@
-#
On Do, 20 Aug 2015, Bram Moolenaar wrote:
I have done the for real update of the Vim repository.
I used the same sequence of commands as for the tryout, thus the result
should be the same.
Did the .gitignore file change between the old googlecode repository and
the new github repository? I
On Di, 25 Aug 2015, Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
I have done the for real update of the Vim repository.
I used the same sequence of commands as for the tryout, thus the result
should be the same.
Did the .gitignore file change between the old
Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
I have done the for real update of the Vim repository.
I used the same sequence of commands as for the tryout, thus the result
should be the same.
Did the .gitignore file change between the old googlecode repository
* Bram Moolenaar b...@moolenaar.net [150821 14:59]:
Looks like most things are ready, I'll soon announce that GitHub is
ready for our business.
What remains to be filled in is the section Moving over to github - if
you have local changes on http://www.vim.org/movetogithub.php
Who has a good
Marvin Reply wrote:
There was a longish thread on debian-devel a while back (I can't find it
right now) about using github for development. One of the points raised
was that if you accept github pull requests (from their web UI), then
those developers who do not have (and perhaps do not
Christian Brabandt wrote:
On Do, 20 Aug 2015, Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
http://www.vim.org/develop.php
also, I think sources.php needs to be adjusted as well.
Looks like most things are ready, I'll soon announce that GitHub is
ready for
Christian Brabandt wrote:
On Do, 20 Aug 2015, Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
http://www.vim.org/develop.php
also, I think sources.php needs to be adjusted as well.
Yes, I'll do that.
--
BEDEVERE: Oh!
LAUNCELOT: No Arrggghhh ...
* Bram Moolenaar b...@moolenaar.net [150821 16:39]:
The idea is that all events on GitHub are forwarded to the vimdev
maillist. Christian had setup something for that. I believe this also
applies to pull requests.
I indeed prefer to discuss changes on the maillist, since everybody can
Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
http://www.vim.org/develop.php
There is a link missing for the mercurial mirror on bitbucket
Added.
However, I think we should move the stuff about using MQ to the
Mercurial page.
I would prefer to have a section on
Am Donnerstag, 20. August 2015, 10:09:39 schrieb Manuel Ortega:
On Thu, Aug 20, 2015 at 4:55 AM, Bram Moolenaar b...@moolenaar.net wrote:
Markus Heidelberg wrote:
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram
Am Donnerstag, 20. August 2015, 10:55:23 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
I have removed the Ubuntu package for hg-fast-export and
On Thu, Aug 20, 2015 at 4:55 AM, Bram Moolenaar b...@moolenaar.net wrote:
Markus Heidelberg wrote:
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
I cloned it - it is perfect :)
For some reason on
Markus Heidelberg wrote:
The biggest file there is 33M. No idea how it gets bigger after pushing
to GitHub. 10M is not something to worry about. Previously it was
600M.
Maybe it has something to do with GitHub's repository management. Or
that the repository was not empty when
On Wednesday, August 19, 2015 at 9:03:52 AM UTC-4, Olaf wrote:
On 19-Aug-15, Bram Moolenaar wrote:
Justin M. Keyes wrote:
...
Why was the _mercurial_ tag format changed in the google code
repository? This breaks all URLs using the old tag format:
Hi vim_dev!
On Do, 20 Aug 2015, Christian Brabandt wrote:
On Do, 20 Aug 2015, Bram Moolenaar wrote:
http://www.vim.org/develop.php
also, I think sources.php needs to be adjusted as well.
Best,
Christian
--
Astrologe:
ein Mensch, der aus den Sternen liest, was im Gesicht steht.
--
--
On Do, 20 Aug 2015, Bram Moolenaar wrote:
http://www.vim.org/develop.php
There is a link missing for the mercurial mirror on bitbucket
I would prefer to have a section on how to migrate from google code to
bitbucket / git.
And if some git expert could write a short explanation on how to
Markus Heidelberg wrote:
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
I have removed the Ubuntu package for hg-fast-export and downloaded the
individual files from repo.or.cz. The conversion now
On 19-Aug-15, Bram Moolenaar wrote:
Justin M. Keyes wrote:
On 8/18/15, Bram Moolenaar b...@moolenaar.net wrote:
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git
Markus Heidelberg wrote:
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
I wrote:
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
I have removed the Ubuntu package for hg-fast-export and downloaded the
individual files from repo.or.cz. The conversion now runs without any
errors or warnings.
The result is now available at
Am Mittwoch, 19. August 2015, 23:15:14 schrieb Markus Heidelberg:
Am Mittwoch, 19. August 2015, 21:35:52 schrieb Bram Moolenaar:
I have removed the Ubuntu package for hg-fast-export and downloaded the
individual files from repo.or.cz. The conversion now runs without any
errors or
On Aug 19, 2015 5:57 PM, Markus Heidelberg markus.heidelb...@web.de
wrote:
Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
On 19-Aug-15, Bram Moolenaar wrote:
Justin M. Keyes wrote:
On 8/18/15, Bram Moolenaar b...@moolenaar.net wrote:
There were a couple of
Am Mittwoch, 19. August 2015, 19:00:36 schrieb Justin M. Keyes:
On Aug 19, 2015 5:57 PM, Markus Heidelberg markus.heidelb...@web.de
wrote:
Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
On 19-Aug-15, Bram Moolenaar wrote:
Justin M. Keyes wrote:
On 8/18/15,
Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
On 19-Aug-15, Bram Moolenaar wrote:
Justin M. Keyes wrote:
On 8/18/15, Bram Moolenaar b...@moolenaar.net wrote:
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination
Am Mittwoch, 19. August 2015, 11:59:12 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
I let the script continue, ignoring the errors. Then I pushed the
result to github. I got some errors, I think my sequence of
Markus Heidelberg wrote:
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
I wrote:
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in
Justin M. Keyes wrote:
On 8/18/15, Bram Moolenaar b...@moolenaar.net wrote:
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git cleanup. I'll hold off until it looks OK,
On Wed, Aug 19, 2015 at 7:25 PM, Markus Heidelberg
markus.heidelb...@web.de wrote:
Am Mittwoch, 19. August 2015, 19:00:36 schrieb Justin M. Keyes:
On Aug 19, 2015 5:57 PM, Markus Heidelberg markus.heidelb...@web.de
wrote:
Am Mittwoch, 19. August 2015, 15:03:38 schrieb Olaf Dabrunz:
On
Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
OK, if there is a chance you still find some improvements for the
Mercurial cleanup, we better wait a bit before doing that.
Once you have it all figured out, I hope you can send me the final
scripts. I wouldn't want some small
Markus Heidelberg wrote:
Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
OK, if there is a chance you still find some improvements for the
Mercurial cleanup, we better wait a bit before doing that.
Once you have it all figured out, I hope you can send me the final
I hope I don't brake the mail chain, I'm not at home at my mail client.
Wonderful! And just in time, I'm working on Vim today.
Then staying up late was worth it :)
So, these are the steps to be taken:
1. Stop making changes: freeze; announce on Google code project page.
Announce on the
Note: I have started doing things for real.
The cleaned up Mercurial repository has been pushed to Google code.
I'll now start the export to github. We can redo this when needed.
In preparation I've renamed the previously exported repo, which was
overwritten with the cleaned up one, to
On Di, 18 Aug 2015, Bram Moolenaar wrote:
Note: I have started doing things for real.
The cleaned up Mercurial repository has been pushed to Google code.
I have resynced the bitbucket mirror. I will update the sync script
tomorrow, when the new github repository should be available. And once
Christian Brabandt wrote:
On Di, 18 Aug 2015, Bram Moolenaar wrote:
Note: I have started doing things for real.
The cleaned up Mercurial repository has been pushed to Google code.
I have resynced the bitbucket mirror. I will update the sync script
tomorrow, when the new github
On 8/18/15, Bram Moolenaar b...@moolenaar.net wrote:
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git cleanup. I'll hold off until it looks OK,
https://github.com/vim/vim-tryout
On 18-Aug-15, Christian Brabandt wrote:
Here is a documentation update:
Stay with mercurial
===
A repository at bitbucket.org has been setup that mirrors the official Vim
source repository at https://github.com/vim/vim
Minor nit-pick:
has been setup - has been set
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git cleanup. I'll hold off until it looks OK,
https://github.com/vim/vim-tryout is what it would look like.
At least it doesn't have the
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
I wrote:
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
working tree.
Use '--' to
I wrote:
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git command [revision...] --
On 18 August 2015, Bram Moolenaar b...@moolenaar.net wrote:
Lcd wrote:
On 18 August 2015, Bram Moolenaar b...@moolenaar.net wrote:
[...]
For users who switch from Mercurial on Google Code to the Mercurial
mirror, there would be an extra commit that doesn't exist anywhere
else. I
On 18 August 2015, Bram Moolenaar b...@moolenaar.net wrote:
[...]
For users who switch from Mercurial on Google Code to the Mercurial
mirror, there would be an extra commit that doesn't exist anywhere
else. I hope that will work.
[...]
Why not make the Bitbucket mirror at the same time as
Markus -
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git command [revision...] -- [file...]'
Lcd wrote:
On 18 August 2015, Bram Moolenaar b...@moolenaar.net wrote:
[...]
For users who switch from Mercurial on Google Code to the Mercurial
mirror, there would be an extra commit that doesn't exist anywhere
else. I hope that will work.
[...]
Why not make the Bitbucket
Markus Heidelberg wrote:
Wonderful! And just in time, I'm working on Vim today.
Then staying up late was worth it :)
And thanks for checking the plan.
So, these are the steps to be taken:
1. Stop making changes: freeze; announce on Google code project page.
Announce on the vim
Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
BTW: you are working on the git cleanup, but is the Mercurial cleanup
now ready to be committed? AFAIK it all looks OK, so I could apply this
to my local repository and push it to Google code,
On Fri, Aug 14, 2015 at 01:39:18AM +0200, Markus Heidelberg wrote:
Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
You mentioned the size of the repository after export to github was
much larger than the one resulting from the local conversion. How do
you see that?
Try
Markus Heidelberg wrote:
Maybe you can comment on some other items from the old mail as well.
Can you repeat the relevant questions?
Oh, not that many remaining which needed clarification. New comments by
myself compared to the old mail after MH:
* Unify name and mail for author
Am Montag, 17. August 2015, 14:49:51 schrieb Marius Gedminas:
On Fri, Aug 14, 2015 at 01:39:18AM +0200, Markus Heidelberg wrote:
Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
You mentioned the size of the repository after export to github was
much larger than the one
Am Freitag, 14. August 2015, 09:42:34 schrieb Christian Brabandt:
Hi Markus!
On Fr, 14 Aug 2015, Markus Heidelberg wrote:
I'd also prefer to just removing the .hgignore from the history and
replacing it with .gitignore. What would that mean for the HG mirror,
Christian?
Hm, I don't
Am Samstag, 15. August 2015, 15:33:54 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
Oh, I just noticed, of course we cannot just use a new git
repository/project on GitHub, otherwise the issues are gone.
The final official repository has to be pushed to one created by the
On So, 16 Aug 2015, Markus Heidelberg wrote:
Am Freitag, 14. August 2015, 09:42:34 schrieb Christian Brabandt:
On Fr, 14 Aug 2015, Markus Heidelberg wrote:
I'd also prefer to just removing the .hgignore from the history and
replacing it with .gitignore. What would that mean for the HG
Markus Heidelberg wrote:
No, that doesn't make a difference. You can remove outdated branches and
tags from the Git repository via git push and overwrite the master
branch by force-pushing.
I found the --mirror argument (among the big pile of arguments that git
has). It appears
Matthew Woehlke wrote:
On 2015-08-14 14:38, Bram Moolenaar wrote:
Hmm, one can add a repository and delete a repository, but making it
totally empty and pushing a fresh repo into it appears not to be
possible.
As far as non-git content (e.g. issues, pull requests), that may be true.
Markus Heidelberg wrote:
Oh, I just noticed, of course we cannot just use a new git
repository/project on GitHub, otherwise the issues are gone.
The final official repository has to be pushed to one created by the
Google exporter therefore.
For the one that's there
Hi Markus!
On Fr, 14 Aug 2015, Markus Heidelberg wrote:
I'd also prefer to just removing the .hgignore from the history and
replacing it with .gitignore. What would that mean for the HG mirror,
Christian?
Hm, I don't know. I guess I can keep it checked in and let git ignore
it.
Best,
Am Freitag, 14. August 2015, 15:05:41 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
Am Freitag, 14. August 2015, 01:39:18 schrieb Markus Heidelberg:
Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
[...]
2.
Markus Heidelberg wrote:
Oh, I just noticed, of course we cannot just use a new git
repository/project on GitHub, otherwise the issues are gone.
The final official repository has to be pushed to one created by the
Google exporter therefore.
For the one that's there now I created
On 2015-08-14 14:38, Bram Moolenaar wrote:
Hmm, one can add a repository and delete a repository, but making it
totally empty and pushing a fresh repo into it appears not to be
possible.
As far as non-git content (e.g. issues, pull requests), that may be true.
To empty out the git bits of a
Am Freitag, 14. August 2015, 20:38:49 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
Oh, I just noticed, of course we cannot just use a new git
repository/project on GitHub, otherwise the issues are gone.
The final official repository has to be pushed to one created by the
Markus Heidelberg wrote:
OK, then I would document a procedure for local HG to Git conversion and
create a script for Git repository cleanup.
I did:
% mkdir vim-git
% cd vim-git
% git init
% hg-fast-export -r ../hg-vim74-clean
On Arch Linux I had to
Markus Heidelberg wrote:
[...]
2. Conversion from HG to Git
So, what we would need to do is use the export to github for whatever
functionality it provides, but then wipe the git repository, do the
conversion from Mercurial to git locally, and
Am Donnerstag, 13. August 2015, 13:14:34 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
[...]
2. Conversion from HG to Git
So, what we would need to do is use the export to github for whatever
functionality it provides, but then wipe
Am Donnerstag, 13. August 2015, 23:01:07 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
OK, then I would document a procedure for local HG to Git conversion and
create a script for Git repository cleanup.
I did:
% mkdir vim-git
% cd vim-git
% git init
%
Markus Heidelberg wrote:
OK, then I would document a procedure for local HG to Git conversion and
create a script for Git repository cleanup.
I did:
% mkdir vim-git
% cd vim-git
% git init
% hg-fast-export -r ../hg-vim74-clean
% git checkout
Looks like it worked. I
Christian Brabandt wrote:
On Sa, 08 Aug 2015, Bram Moolenaar wrote:
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
Markus Heidelberg wrote:
sorry for the late reply. I'm pretty busy and also needed a bit to find
the proper words. It also takes some time to get into this topic again
after several months of silence.
Thanks for the long reply.
Am Samstag, 8. August 2015, 21:43:13 schrieb Bram Moolenaar:
Am Mittwoch, 12. August 2015, 23:20:21 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
1. Cleanup in the HG repository
***
a check whether the rebase extension is enabled.
I think I already have it enabled, my .hgrc contains:
[extensions]
Hi Bram,
sorry for the late reply. I'm pretty busy and also needed a bit to find
the proper words. It also takes some time to get into this topic again
after several months of silence.
Am Samstag, 8. August 2015, 21:43:13 schrieb Bram Moolenaar:
Markus Heidelberg wrote:
For me, a proper
On Sa, 08 Aug 2015, Bram Moolenaar wrote:
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
On Wed, Aug 12, 2015 at 6:51 AM, Markus Heidelberg #!/bin/sh
# Vim HG repository cleanup
hg config extensions.rebase || (echo -e Rebase extension has to be enabled
in ~/.hgrc:\n[extensions]\nrebase = exit 1)
The exit 1 above won't exit the shell script - it exits only the
subshell. Perhaps
Am Mittwoch, 12. August 2015, 08:50:55 schrieb Nazri Ramliy:
On Wed, Aug 12, 2015 at 6:51 AM, Markus Heidelberg #!/bin/sh
# Vim HG repository cleanup
hg config extensions.rebase || (echo -e Rebase extension has to be enabled
in ~/.hgrc:\n[extensions]\nrebase = exit 1)
The exit 1
I wrote:
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
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
On 4/16/2015 1:33 PM, Nikolay Pavlov wrote:
More powerful?! Try to add phases/changeset obsolescense/branches/etc to git.
The point is that this “sharper knife” has an architecture that
prevents adding feature to the core. You can do almost anything with
the core using plugins for mercurial,
2015-04-16 9:36 GMT+03:00 Roland Eggner ed...@systemanalysen.net:
On 2015-04-14 Tuesday at 20:00 +0300 Nikolay Pavlov wrote:
2015-04-14 17:37 GMT+03:00 Roland Eggner ed...@systemanalysen.net:
@Bram, @Christian, @all
───
During some 10 years of almost daily usage of
Hi Markus!
On Mi, 15 Apr 2015, Markus Heidelberg wrote:
Am Dienstag, 14. April 2015, 20:02:17 schrieb Christian Brabandt:
Ubuntu 12.04 LTS:
Mercurial Distributed SCM (version 2.0.2)
(see http://mercurial.selenic.com for more information)
Huh, pretty old from 2012-01-01 :)
You know,
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase --dest tip~7 --source tip~6 --collapse -mAdd missing tags
I was brave and tested your script. There are two points I noticed.
1) rebase needs to be
2015-04-14 17:37 GMT+03:00 Roland Eggner ed...@systemanalysen.net:
On 2015-04-13 Monday at 20:00 +0200 Christian Brabandt wrote:
On Mo, 13 Apr 2015, Bram Moolenaar wrote:
Markus Heidelberg wrote:
Some things can perhaps be done on the Mercurial repository before the
import, but I
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase --dest tip~7 --source tip~6 --collapse -mAdd missing tags
I was brave and tested your script. There
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase --dest tip~7 --source tip~6 --collapse -mAdd missing tags
I was brave and tested your script. There are two points I noticed.
1) rebase needs to be enabled explicitly in your .hg/hgrc
2) hg rebase does not seem to
On Di, 14 Apr 2015, Christian Brabandt wrote:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase --dest tip~7 --source tip~6 --collapse -mAdd
On 2015-04-13 Monday at 20:00 +0200 Christian Brabandt wrote:
On Mo, 13 Apr 2015, Bram Moolenaar wrote:
Markus Heidelberg wrote:
Some things can perhaps be done on the Mercurial repository before the
import, but I suppose some are only possible in git. What will happen
for the
2015-04-14 21:02 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase --dest tip~7 --source tip~6
2015-04-14 21:36 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 21:02 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi
2015-04-14 21:50 GMT+03:00 Nikolay Pavlov zyx@gmail.com:
2015-04-14 21:36 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 21:02 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14
Hello Christian and Nikolay
Am Dienstag, 14. April 2015, 20:02:17 schrieb Christian Brabandt:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
[...]
hg rebase
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 21:02 GMT+03:00 Christian Brabandt cbli...@256bit.org:
On Di, 14 Apr 2015, Nikolay Pavlov wrote:
2015-04-14 20:45 GMT+03:00 Christian Brabandt cbli...@256bit.org:
Hi Markus!
On Mo, 13 Apr 2015, Markus Heidelberg wrote:
On Mo, 13 Apr 2015, Bram Moolenaar wrote:
Markus Heidelberg wrote:
Hello Bram,
currently I'm pretty busy aside from computer, so it all takes a while.
But here it is, the first part of cleanup in HG. A Git cleanup process
will follow after having finished this step.
Am Mittwoch, 1.
Markus Heidelberg wrote:
Hello Bram,
currently I'm pretty busy aside from computer, so it all takes a while.
But here it is, the first part of cleanup in HG. A Git cleanup process
will follow after having finished this step.
Am Mittwoch, 1. April 2015, 21:52:41 schrieb Bram Moolenaar:
Hello Bram,
currently I'm pretty busy aside from computer, so it all takes a while.
But here it is, the first part of cleanup in HG. A Git cleanup process
will follow after having finished this step.
Am Mittwoch, 1. April 2015, 21:52:41 schrieb Bram Moolenaar:
I generally like cleaning up,
Hi Bram!
On Mi, 01 Apr 2015, Bram Moolenaar wrote:
What will happen for the mirror in Mercurial then?
If you mean the bitbucket mirror I have set up, I wouldn't be too
concerned.
First of all, it is currently in experimental state, until I figure out
the complete workflow for git and how I
High Markus!
On 2015-04-01 Wednesday at 08:50 +0300 LCD 47 wrote:
On 1 April 2015, Markus Heidelberg markus.heidelb...@web.de wrote:
if switching to Git, we could seriously consider cleaning up the
repository, now it might be the last chance for quite a while.
I have collected some
I'm not sure why everyone seems to think the Vim development process is going
to change drastically just because Bram is moving Vim to Github. A lot of that
stuff you're daydreaming about is also possible with Mercurial, and Bram has
resisted significant changes there for a long time. Although
Hi Ben!
On Mi, 01 Apr 2015, Ben Fritz wrote:
I'm not sure why everyone seems to think the Vim development process
is going to change drastically just because Bram is moving Vim to
Github. A lot of that stuff you're daydreaming about is also possible
with Mercurial, and Bram has resisted
Ben Fritz wrote:
On Friday, March 27, 2015 at 4:06:47 PM UTC-5, Bruno Sutic wrote:
- lastly, it has been mentioned a couple times vim plugin community is
already on github. The objective statement that proves this: github
currently has 42,636 vim related repositories, bitbucket has only 1652
Markus Heidelberg wrote:
if switching to Git, we could seriously consider cleaning up the
repository, now it might be the last chance for quite a while.
I have collected some possibilities for improvement - some simple, some
a bit more complicated, but if found the proper commands/scripts,
2015-04-01 22:52 GMT+03:00 Bram Moolenaar b...@moolenaar.net:
Markus Heidelberg wrote:
if switching to Git, we could seriously consider cleaning up the
repository, now it might be the last chance for quite a while.
I have collected some possibilities for improvement - some simple, some
a
1 - 100 din 183 matches
Mail list logo
