Preparations for moving to github

Since Google Code is going to be shut down we need a new place for the Vim repository. Many users have given their opinion and github appears to be the preferred site. This is not without disadvantages, since it means moving from Mercurial to git. Some may like this, some not. Will take some g

Re: Preparations for moving to github

* Bram Moolenaar [2015-03-24 22:36 +0100]: > > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > > This is not without disadvantages, since it means moving from Mercurial

Re: Preparations for moving to github

* Bram Moolenaar [2015-03-24 22:36 +0100]: > > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > > This is not without disadvantages, since it means moving from Mercurial

Re: Preparations for moving to github

Elimar Riesebieter wrote: > * Bram Moolenaar [2015-03-24 22:36 +0100]: > > > > > Since Google Code is going to be shut down we need a new place for the > > Vim repository. Many users have given their opinion and github appears > > to be the preferred site. > > > > This is not without disadva

Re: Preparations for moving to github

> I do have the tags in my local git repository. Do they not get pushed > to the repository with "git push" ? v7-4-678 would be the last one that > was imported, the patches after that I pushed from my git repository. Please try "--tags" option to push. Like this: $ git push --tags Regards

Re: Preparations for moving to github

* Bram Moolenaar [2015-03-24 23:36 +0100]: > > Elimar Riesebieter wrote: [...] > > The tags don't seem to correspond to the latest patch version? > > I do have the tags in my local git repository. Do they not get pushed > to the repository with "git push" ? v7-4-678 would be the last one that

Re: Preparations for moving to github

On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > > This is not without disadvantages, since it mean

Re: Preparations for moving to github

On Tue, Mar 24, 2015 at 11:36:02PM +0100, Bram Moolenaar wrote: > > I do have the tags in my local git repository. Do they not get pushed > to the repository with "git push" ? No, one always has to use 'git push && git push --tags'. It's one of the biggest warts of Git IMHO. (This being git th

Re: Preparations for moving to github

Giuseppe Bilotta wrote: > On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > > Since Google Code is going to be shut down we need a new place for the > > Vim repository. Many users have given their opinion and github appears > > to be the preferred site. > > > > This is no

Re: Preparations for moving to github

Taro Muraoka wrote: > > I do have the tags in my local git repository. Do they not get pushed > > to the repository with "git push" ? v7-4-678 would be the last one that > > was imported, the patches after that I pushed from my git repository. > > Please try "--tags" option to push. Like this

Re: Preparations for moving to github

2015-03-25 19:21 GMT+09:00 Bram Moolenaar : >> $ git push --tags > > See, that's why git is more difficult than Mercurial, so many hidden > flags and options. Yes, I agree entirely. Additionally, there are many sub-commands and options which are hard to imagine feature/behavior from its name. O

Re: Preparations for moving to github

On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > > This is not without disadvantages, since it mean

Re: Preparations for moving to github

Am 2015-03-25 16:21, schrieb Bruno Sutic: - http://www.vim.org/develop.php I don't know yet, what the process will look like. Until now, I have been using mercurials mq extension but not sure how to proceed here. Perhaps using feature branches is all what is needed... I'm curious, when a s

Re: Preparations for moving to github

On Wed, Mar 25, 2015 at 11:47 AM, Christian Brabandt wrote: > Am 2015-03-25 16:21, schrieb Bruno Sutic: [snip] >> I'm curious, when a switch is made, will Github's "pull request" >> feature be used? Or will code contributions still be done with patches >> via mailing list? > > > I don't know. But

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic wrote: > I'm curious, when a switch is made, will Github's "pull request" feature be > used? Or will code contributions still be done with patches via mailing list? > > I'd guess a move to "pull request" workflow will be done since it

Re: Preparations for moving to github

There are some helpers for git hub that may be useful. I use this one: https://github.com/ingydotnet/git-hub works with cygwin on windows, and is perfect for linux environment. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you ar

Re: Preparations for moving to github

On 25 March 2015, Ben Fritz wrote: > On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic wrote: > > I'm curious, when a switch is made, will Github's "pull request" > > feature be used? Or will code contributions still be done with > > patches via mailing list? > > > > I'd guess a move

Re: Preparations for moving to github

On 3/25/2015 12:12 AM, Marius Gedminas wrote: On Tue, Mar 24, 2015 at 11:36:02PM +0100, Bram Moolenaar wrote: I do have the tags in my local git repository. Do they not get pushed to the repository with "git push" ? No, one always has to use 'git push && git push --tags'. It's one of the bigg

Re: Preparations for moving to github

On 3/25/2015 10:18 AM, LCD 47 wrote: On 25 March 2015, Ben Fritz wrote: I think it would be nice to have an "official" Mercurial mirror, which isn't possible at GitHub. And I think an official mirror will be harder to maintain if we need to use multiple sites for it, especially if each site ha

Re: Preparations for moving to github

On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > > This is not without disadvantages, since it mean

Re: Preparations for moving to github

Hi Ernie! On Mi, 25 Mär 2015, Ernie Rael wrote: >...on twitter, "generates a random man page for a made-up >git command... more or less indistinguishable from the official docs" > >http://git-man-page-generator.lokaltog.net/ Hah, that one is great! Best, Christian -- Abstinenz: d

Re: Preparations for moving to github

Hi Bruno! On Mi, 25 Mär 2015, Bruno Sutic wrote: > On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > > Since Google Code is going to be shut down we need a new place for the > > Vim repository. Many users have given their opinion and github appears > > to be the preferred

Re: Preparations for moving to github

Hi John! On Mi, 25 Mär 2015, John Szakmeister wrote: > On Wed, Mar 25, 2015 at 11:47 AM, Christian Brabandt > wrote: > > Am 2015-03-25 16:21, schrieb Bruno Sutic: > [snip] > >> I'm curious, when a switch is made, will Github's "pull request" > >> feature be used? Or will code contributions stil

Re: Preparations for moving to github

On 25 March 2015, Christian Brabandt wrote: > Hi Bruno! > > On Mi, 25 Mär 2015, Bruno Sutic wrote: [...] > > This is great news. > > From what I can tell, the reactions to this post on reddit vim > > group, twitter and hacker news have been very positive. > > > > I volunteered to help in the pre

Re: Preparations for moving to github

I am very excited that Github is being considered. It has become something of a standard for open source software these days, for better or worse, it's what most people are using which I think is good for Vim. For those of you unfamiliar with Git, I HIGHLY recommend reading this free book: http

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 12:18:46 PM UTC-5, LCD 47 wrote: > On 25 March 2015, Ben Fritz wrote: > > On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic wrote: > > > I'm curious, when a switch is made, will Github's "pull request" > > > feature be used? Or will code contributions st

Re: Preparations for moving to github

Not sure if I'm missing something but to organize multiple repositories all you have to do is to create a Github organization described here https://help.github.com/articles/creating-a-new-organization-account/ -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type

Re: Preparations for moving to github

Bruno Sutic wrote: > This is great news. > From what I can tell, the reactions to this post on reddit vim group, twitter > and hacker news have been very positive. > > I volunteered to help in the previous thread about moving away from > Google Code.. so if help is needed with drafting or testi

Re: Preparations for moving to github

Christian Brabandt wrote: [...] > @Bram, perhaps it is necessary to split the runtime directory into a > separate > github repository, so they could be easier handled. How is that easier? Most users will want just one repo to pull from and rebuild their local Vim, possibly with some local cha

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 7:52:44 PM UTC+1, Christian Brabandt wrote: > Hi Bruno! > > On Mi, 25 Mär 2015, Bruno Sutic wrote: > > > On Tuesday, March 24, 2015 at 10:36:32 PM UTC+1, Bram Moolenaar wrote: > > > Since Google Code is going to be shut down we need a new place for the > > > Vim re

Re: Preparations for moving to github

On Tue, Mar 24, 2015 at 5:36 PM, Bram Moolenaar wrote: > > Since Google Code is going to be shut down we need a new place for the > Vim repository. Many users have given their opinion and github appears > to be the preferred site. > Darn. It would be nice if, when this gets finalized, the new

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 3:35:21 PM UTC-5, Martin Lundberg wrote: > Not sure if I'm missing something but to organize multiple repositories all > you have to do is to create a Github organization described here > https://help.github.com/articles/creating-a-new-organization-account/ You're

Re: Preparations for moving to github

Manuel Ortega wrote: > On Tue, Mar 24, 2015 at 5:36 PM, Bram Moolenaar wrote: >> >> >> Since Google Code is going to be shut down we need a new place for the >> Vim repository. Many users have given their opinion and github appears >> to be the preferred site. > > > Darn. > > It would be nice i

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 6:47:48 PM UTC+3, Christian Brabandt wrote: > I don't know yet, what the process will look like. Until now, I have > been using mercurials mq extension > but not sure how to proceed here. There is a stgit (http://procode.org/stgit/) with similar functionality. --

Re: Preparations for moving to github

On 25 March 2015, Ben Fritz wrote: > On Wednesday, March 25, 2015 at 12:18:46 PM UTC-5, LCD 47 wrote: > > On 25 March 2015, Ben Fritz wrote: > > > On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic > > > wrote: > > > > I'm curious, when a switch is made, will Github's "pull request" >

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 12:43 AM, Dominique Pellé wrote: > Manuel Ortega wrote: > > > > It would be nice if, when this gets finalized, the new repo trims out > > ancient stuff like 7.0, 7.1, and 7.2. There's no reason for everyone to > > have to clone all that and carry it around on disk. Yes,

Re: Preparations for moving to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26-Mar-2015 14:32, Manuel Ortega wrote: > It's smaller than Linux, therefore it's not too big? It's far too > big for the kind of thing it is. It's a plain text editor; a user > shouldn't have 50MB worth of useless things (much from *eleven* > yea

Re: Preparations for moving to github

Am 2015-03-25 21:48, schrieb Bram Moolenaar: Christian Brabandt wrote: [...] @Bram, perhaps it is necessary to split the runtime directory into a separate github repository, so they could be easier handled. How is that easier? Most users will want just one repo to pull from and rebuild th

Re: Preparations for moving to github

On Mar 25, 2015 7:18 PM, "Manuel Ortega" wrote: > > On Tue, Mar 24, 2015 at 5:36 PM, Bram Moolenaar wrote: >> >> >> Since Google Code is going to be shut down we need a new place for the >> Vim repository. Many users have given their opinion and github appears >> to be the preferred site. > > >

Re: Preparations for moving to github

Hi there, On Thu, Mar 26, 2015 at 09:32:32AM -0400, Manuel Ortega wrote: > On Thu, Mar 26, 2015 at 12:43 AM, Dominique Pellé wrote: > > Manuel Ortega wrote: > > or find out when a piece of code was changed and why. > Bram can (and should) put older parts under github.com/vim/70 and > github.co

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 9:43 AM, Ingo Karkat wrote: > > > Bram already is a bottleneck in development; please don't make him > work harder by adding yet more complexity in repo maintenance! > > It's quite obvious that almost nobody on this list cares about adding complexity for Bram; it they d

Re: Preparations for moving to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26-Mar-2015 17:25, Manuel Ortega wrote: > On Thu, Mar 26, 2015 at 9:43 AM, Ingo Karkat > wrote: > >> Bram already is a bottleneck in development; please don't make >> him > > work harder by adding yet more complexity

Re: Preparations for moving to github

Manuel Ortega wrote: > On Tue, Mar 24, 2015 at 5:36 PM, Bram Moolenaar wrote: > > > > > Since Google Code is going to be shut down we need a new place for the > > Vim repository. Many users have given their opinion and github appears > > to be the preferred site. > > > > Darn. > > It would b

Re: Preparations for moving to github

* James McCoy [2015-03-26 11:26 -0400]: [...] > $ git clone https://github.com/vim/vim > ... > $ cd vim > $ du -hs .git . > 685M.git > 47M . > $ git gc --aggressive > ... > $ du -hs .git . > 34M .git > 47M . > > For reference, are similar numbers for a fresh Mercurial clone: >

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 11:26 AM, James McCoy wrote: [snip] > $ git gc --aggressive > ... > $ du -hs .git . > 34M .git > 47M . Just wanted to point out that there's really no need for "--aggressive" here. "git gc" without it will often produce similar results in less time. :-) -John --

Re: Preparations for moving to github

On Friday, March 27, 2015 at 5:00:19 AM UTC+9, Bram Moolenaar wrote: > Isn't there a way to clone only up to some time ago, e.g., the 7.4 > release? I rather leave this a decision on the user side than on the > server side (meaning that history would be lost forever). git clone --depth 1 -- --

Re: Preparations for moving to github

On Mar 26, 2015 5:03 PM, "John Szakmeister" wrote: > > On Thu, Mar 26, 2015 at 11:26 AM, James McCoy wrote: > [snip] > > $ git gc --aggressive > > ... > > $ du -hs .git . > > 34M .git > > 47M . > > Just wanted to point out that there's really no need for > "--aggressive" here. "git gc" w

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 7:44 PM, James McCoy wrote: > > On Mar 26, 2015 5:03 PM, "John Szakmeister" wrote: > > > > On Thu, Mar 26, 2015 at 11:26 AM, James McCoy > wrote: > > [snip] > > > $ git gc --aggressive > > > ... > > > $ du -hs .git . > > > 34M .git > > > 47M . > > > > Just wanted

Re: Preparations for moving to github

On Tuesday, March 24, 2015 at 4:36:32 PM UTC-5, Bram Moolenaar wrote: > > Look here: https://github.com/vim > > Please respond to the list if something doesn't work well. > When I click the "branches" tab I get a Unicorn! error page saying "This page is taking way too long to load." Somehow I

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 08:25:12PM -0700, Ben Fritz wrote: > On Tuesday, March 24, 2015 at 4:36:32 PM UTC-5, Bram Moolenaar wrote: > > > > Look here: https://github.com/vim > > > > Please respond to the list if something doesn't work well. > > > > When I click the "branches" tab I get a Unicorn

Re: Preparations for moving to github

James McCoy : > $ git clone https://github.com/vim/vim > ... > $ cd vim > $ du -hs .git . > 685M.git > 47M . > $ git gc --aggressive > ... > $ du -hs .git . > 34M .git > 47M . The Google Code to GitHub exporter seems to do a pretty bad job at finding good deltas; I've seen other pr

Re: Preparations for moving to github

On Fri, Mar 27, 2015 at 04:42:31PM +1300, Jan Larres wrote: > James McCoy : > > $ git clone https://github.com/vim/vim > > ... > > $ cd vim > > $ du -hs .git . > > 685M.git > > 47M . > > $ git gc --aggressive > > ... > > $ du -hs .git . > > 34M .git > > 47M . > > The Google Code to

Re: Preparations for moving to github

On Thu, Mar 26, 2015 at 8:48 PM, Manuel Ortega wrote: [snip] > While "git gc" will *sometimes* produce similar results to "git gc > --aggressive", it very, very often in my experience does not. This is > perhaps one of those cases. --aggressive is really about letting Git go back and giving it a

Re: Preparations for moving to github

El Thursday 26 March 2015, Christian Brabandt escribió: > Am 2015-03-25 21:48, schrieb Bram Moolenaar: > > Christian Brabandt wrote: > > > > [...] > > > >> @Bram, perhaps it is necessary to split the runtime directory into a > >> separate > >> github repository, so they could be easier handled. >

Re: Preparations for moving to github

Marius Gedminas wrote: > On Fri, Mar 27, 2015 at 04:42:31PM +1300, Jan Larres wrote: > > James McCoy : > > > $ git clone https://github.com/vim/vim > > > ... > > > $ cd vim > > > $ du -hs .git . > > > 685M.git > > > 47M . > > > $ git gc --aggressive > > > ... > > > $ du -hs .git . > > > 3

Re: Preparations for moving to github

Kana Natsuno wrote: > On Friday, March 27, 2015 at 5:00:19 AM UTC+9, Bram Moolenaar wrote: > > Isn't there a way to clone only up to some time ago, e.g., the 7.4 > > release? I rather leave this a decision on the user side than on the > > server side (meaning that history would be lost forever).

Re: Preparations for moving to github

On Friday, March 27th, 2015 at 9:11AM, Bram Moolenaar wrote: > > Kana Natsuno wrote: > > > On Friday, March 27, 2015 at 5:00:19 AM UTC+9, Bram Moolenaar wrote: > > > Isn't there a way to clone only up to some time ago, e.g., the 7.4 > > > release? I rather leave this a decision on the user side

Re: Preparations for moving to github

On Fri, Mar 27, 2015 at 9:13 AM, Peter Aronoff wrote: > On Friday, March 27th, 2015 at 9:11AM, Bram Moolenaar wrote: > > > > Kana Natsuno wrote: > > > > > On Friday, March 27, 2015 at 5:00:19 AM UTC+9, Bram Moolenaar wrote: > > > > Isn't there a way to clone only up to some time ago, e.g., the 7.

Re: Preparations for moving to github

On Friday, March 27th, 2015 at 9:47AM, Manuel Ortega wrote: > No, that's not the case. You can just do a regular git pull. I do this > all the time with other repos that I shallowly clone, such as Homebrew. > > If you *want* to pull in the full history after starting with a shallow > clone, then

Re: Preparations for moving to github

I'd just like to point out that all you githeads arguing over the various different options on pull and fetch and whether they break or keep your repository intact, are making me VERY sad about losing Mercurial. Bram, is there a chance you'd be willing to also push to a Mercurial mirror using o

Re: Preparations for moving to github

Hi Ben! On Fr, 27 Mär 2015, Ben Fritz wrote: > I'd just like to point out that all you githeads arguing over the > various different options on pull and fetch and whether they break or > keep your repository intact, are making me VERY sad about losing > Mercurial. > > Bram, is there a chance you

Re: Preparations for moving to github

On Friday, March 27, 2015 at 11:28:42 AM UTC-5, Christian Brabandt wrote: > > If I have understood correctly, it's easy enough to setup a mirror > somewhere else. If that is straightforward, I could set it up for github > to mirror somewhere else (bitbucket?) > Yes, it's pretty easy to set up

Re: Preparations for moving to github

Ben Fritz wrote: > I'd just like to point out that all you githeads arguing over the > various different options on pull and fetch and whether they break or > keep your repository intact, are making me VERY sad about losing > Mercurial. Keep in mind that 95% of the users will only use the very s

Re: Preparations for moving to github

Christian Brabandt wrote: > Hi Ben! > > On Fr, 27 Mär 2015, Ben Fritz wrote: > > > I'd just like to point out that all you githeads arguing over the > > various different options on pull and fetch and whether they break or > > keep your repository intact, are making me VERY sad about losing > >

Re: Preparations for moving to github

On Fri, Mar 27, 2015 at 12:18 PM, Bram Moolenaar wrote: > > Bram, is there a chance you'd be willing to also push to a Mercurial > > mirror using one of the various bridge methods, either automatically > > via repository hook or manually when you push patches to the public > > repo? > > I do not p

Re: Preparations for moving to github

On Mar 27, 2015 1:32 PM, "Benjamin Fritz" wrote: > If we use Bitbucket (or another service that supports both), nobody > needs to learn a new tool. And we can combine both repositories together > under one project page. People could clone server-side from either > repository depending on their sys

Re: Preparations for moving to github

On Friday, March 27, 2015 at 1:21:48 PM UTC-5, James McCoy wrote: > Why should this be different than any other open source project?  If > you want to contribute, you need to learn the tools that are being > used. When tools change, then something different needs to be learned. > It's not up to the

Re: Preparations for moving to github

Ben: I would argue that Github provides a huge variety of useful tools to manage Vim that will net a major net positive going forward. Having a central place for issues and patches that is very familiar to many developers will help to make the barrier of entry for new contributors far lower as

Re: Preparations for moving to github

On 03/27/2015 12:00, Ben Fritz wrote: On Friday, March 27, 2015 at 1:21:48 PM UTC-5, James McCoy wrote: Why should this be different than any other open source project? If you want to contribute, you need to learn the tools that are being used. When tools change, then something different needs

Re: Preparations for moving to github

> > > We can't forget either that a MAJOR part of the Vim plugin ecosystem lives > on Github already. I don't know why people keep bringing this up. It's (a) not even clear that it is true, and (b) even if it is true, it strikes me as completely irrelevant to the question of where to host vim.

Re: Preparations for moving to github

> Indeed, we haven't even seen *that* reason.  All we've seen is "it makes the > vocal git users happy".  I don't know why people keep saying "the majority of > vim users prefer git/github".  This has in no way been established.  The > "poll" this thread created shouldn't be assumed to be a repr

Re: Preparations for moving to github

On Fri, Mar 27, 2015 at 5:06 PM, Bruno Sutic wrote: > > Indeed, we haven't even seen *that* reason. All we've seen is "it makes > the vocal git users happy". I don't know why people keep saying "the > majority of vim users prefer git/github". This has in no way been > established. The "poll"

Re: Preparations for moving to github

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 > (this is based

Re: Preparations for moving to github

Bram- Just a quick comment, followed by a maintenance question: First: Despite being a long time git and github user, I would still vote that you go with your personal preference by sticking with hg. I feel that much of the vim development cycle is built on your personal style of development,

Re: Preparations for moving to github

Marshall Ward wrote: > Bram- > Just a quick comment, followed by a maintenance question: > > First: > > Despite being a long time git and github user, I would still vote that > you go with your personal preference by sticking with hg. I feel that > much of the vim development cycle is built on

Re: Preparations for moving to github

On Wednesday, March 25, 2015 at 11:48:42 PM UTC+3, Bram Moolenaar wrote: > Christian Brabandt wrote: > > [...] > > > @Bram, perhaps it is necessary to split the runtime directory into a > > separate > > github repository, so they could be easier handled. > > How is that easier? Most users will

Re: Preparations for moving to github

On Saturday, March 28, 2015 at 5:11:26 PM UTC+3, Bram Moolenaar wrote: > Marshall Ward wrote: > > > Bram- > > Just a quick comment, followed by a maintenance question: > > > > First: > > > > Despite being a long time git and github user, I would still vote that > > you go with your personal pref

Re: Preparations for moving to github

On Sun, Mar 29, 2015 at 05:29:51AM -0700, ZyX wrote: > This still has downsides comparing to single repository: > 1. PRs to runtime will now be scattered between /runtime/ repository and / > repository. > 2. Duplicate history entries in /runtime/ and /. > 3. Requirement to do two-way synchronizati

Re: Preparations for moving to github

ZyX wrote: [...] > > > But the serious question: > > > > > > How will this work for syntax maintainers? In the past, we just send > > > patches to the maintainers, who would then pass them along to you. > > > Should we now send pull requests directly to the repo, and the > > > maintainer can j

Re: Preparations for moving to github

2015-03-29 18:56 GMT+03:00 Bram Moolenaar : > > ZyX wrote: > > [...] > >> > > But the serious question: >> > > >> > > How will this work for syntax maintainers? In the past, we just send >> > > patches to the maintainers, who would then pass them along to you. >> > > Should we now send pull reques

Re: Preparations for moving to github

On 29 March 2015, Nikolay Pavlov wrote: > 2015-03-29 18:56 GMT+03:00 Bram Moolenaar : > > > > ZyX wrote: > > > > [...] > > > >> > > But the serious question: > >> > > > >> > > How will this work for syntax maintainers? In the past, we > >> > > just send patches to the maintainers, who would then

Re: Preparations for moving to github

On Fr, 27 Mär 2015, Bram Moolenaar wrote: > Christian Brabandt wrote: > > On Fr, 27 Mär 2015, Ben Fritz wrote: > > > > > I'd just like to point out that all you githeads arguing over the > > > various different options on pull and fetch and whether they break or > > > keep your repository intact,

Re: Preparations for moving to github

On 3/30/2015 8:16 AM, Christian Brabandt wrote: On Fr, 27 Mär 2015, Bram Moolenaar wrote: Christian Brabandt wrote: On Fr, 27 Mär 2015, Ben Fritz wrote: I'd just like to point out that all you githeads arguing over the various different options on pull and fetch and whether they break or kee

Re: Preparations for moving to github

On 30 March 2015, Christian Brabandt wrote: > I have setup a mercurial mirror here: > https://bitbucket.org/vim-mirror/vim > (as a bonus, this is a clone of the official google code repository, so > it contains all commits from there). [...] Your manual commits are shown as "draft". A quick

Re: Preparations for moving to github

Hi LCD! On Mo, 30 Mär 2015, LCD 47 wrote: > On 30 March 2015, Christian Brabandt wrote: > > I have setup a mercurial mirror here: > > https://bitbucket.org/vim-mirror/vim > > (as a bonus, this is a clone of the official google code repository, so > > it contains all commits from there). > [...]

Re: Preparations for moving to github

On Mon, Mar 30, 2015 at 07:16:40PM +0200, Christian Brabandt wrote: > On Mo, 30 Mär 2015, LCD 47 wrote: > > On 30 March 2015, Christian Brabandt wrote: > > > I have setup a mercurial mirror here: > > > https://bitbucket.org/vim-mirror/vim > > > (as a bonus, this is a clone of the official google c

Re: Preparations for moving to github

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

Repository cleanup (Was: Preparations for moving to github)

Hi, 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, the automated tasks should

Re: Repository cleanup (Was: Preparations for moving to github)

On 1 April 2015, Markus Heidelberg wrote: > Hi, > > 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 t

Re: Repository cleanup (Was: Preparations for moving to github)

High Markus! On 2015-04-01 Wednesday at 08:50 +0300 LCD 47 wrote: > On 1 April 2015, 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 im

Re: Repository cleanup (Was: Preparations for moving to github)

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 I

Re: Repository cleanup (Was: Preparations for moving to github)

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 s

Re: Repository cleanup (Was: Preparations for moving to github)

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/scri

Re: Repository cleanup (Was: Preparations for moving to github)

2015-04-01 22:52 GMT+03:00 Bram Moolenaar : > > 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 mor

Re: Repository cleanup (Was: Preparations for moving to github)

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

Re: Repository cleanup (Was: Preparations for moving to github)

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, b

Re: Repository cleanup (Was: Preparations for moving to github)

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 Moolen

Re: Repository cleanup (Was: Preparations for moving to github)

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 M

Re: Repository cleanup (Was: Preparations for moving to github)

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 > > >

Re: Repository cleanup (Was: Preparations for moving to github)

2015-04-14 17:37 GMT+03:00 Roland Eggner : > 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 a

  1   2   >