Re: [Toolserver-l] Pywikibot, GIT and TS
On 10/08/13 13:05, Dr. Trigon wrote: If you read the instructions (https://www.mediawiki.org/wiki/Manual:Pywikipediabot/Gerrit), it recommends you only clone with a --depth of 3 (or anything smaller), and it will take up very little space. Yes of course there is a solution - but it again one thing that can go wrong and another paramter you have to remeber and use. By the way it would be a good thing if it would be possible to develop from TS also. And then all the 200MB are needed, aren't they? No, they aren't. You can happily develop from a shadow clone. You would only have problems if someone sent you a patchset based on an old version you didn't clone (but when working from gerrit, it won't happen). You would of course not have the commits previous to the point you set, so you won't be able to properly view the commit list or blame. But that's not a big difference with svn, where those requiring downloading the full file history from the net (I went to ViewVC for those actions). In git they are nice with a full clone, but they won't work properly with a shallow clone (eg. they will attribute everything “old” to the earliest commit you cloned). ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
[Toolserver-l] Pywikibot, GIT and TS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all! Pywikibot finished GIT migration. Now a question has anybody ever tryed to clone and use the e.g. the pywikibot/compat repo on the TS? If I do, I get and .git folder of about 200MB which nearly fills my home quota. (this is the plain clone - nothing done to/with it yet!!) Yes I could do 'git gc' I could also switch to using SVN from github (but needs to handle all externals manually)... So... what was acutally the reason for switching to GIT? Despite the fact that I have to enter about 1 million different commands now (in SVN I needed 5 ... maybe 10 - 1 command per action, in GIT I need about 5-10 command PER action) I am dealing 75% of my time with GIT issues (that SVN did not have)... In fact I am not able to to USE or further develop the GIT repo since the migration - and I am SERIOUSLY thinking about setting up an own copy on sf.net again and work there... (then we would also have the bug-tracker back in the same place) At the moment I see just 2 drawbacks: 1.) not hosted by mediawiki (really a drawback?) 2.) no review (this is the one and only advantage of git till now, and in fact it's git-review which causes issues too) The list of advantages on the other side, is that long that I will not even start making one, think of it yourself and please give me some feedback! At least I do not see if there will ever be a point in time when GIT will start to work as well as SVN did in the past. I do also not see why I have to enter 5 commands just to make a simple commit. And that will never change... Thanks for your thoughts and Greetings DrTrigon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIGBzQACgkQAXWvBxzBrDC40gCeNt8b7KoBLV9BDNDojjM01Upp ZsEAoIQIJ7W1FGMNysOE7LIp4qi25pyW =mvrX -END PGP SIGNATURE- ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Pywikibot, GIT and TS
On Sat, Aug 10, 2013 at 5:26 PM, Dr. Trigon dr.tri...@surfeu.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all! Pywikibot finished GIT migration. Now a question has anybody ever tryed to clone and use the e.g. the pywikibot/compat repo on the TS? If I do, I get and .git folder of about 200MB which nearly fills my home quota. (this is the plain clone - nothing done to/with it yet!!) If you read the instructions ( https://www.mediawiki.org/wiki/Manual:Pywikipediabot/Gerrit), it recommends you only clone with a --depth of 3 (or anything smaller), and it will take up very little space. Yes I could do 'git gc' I could also switch to using SVN from github (but needs to handle all externals manually)... So... what was acutally the reason for switching to GIT? Despite the fact that I have to enter about 1 million different commands now (in SVN I needed 5 ... maybe 10 - 1 command per action, in GIT I need about 5-10 command PER action) I am dealing 75% of my time with GIT issues (that SVN did not have)... I don't follow. git commit filename.py, git review -R, and then hit +2. In fact I am not able to to USE or further develop the GIT repo since the migration - and I am SERIOUSLY thinking about setting up an own copy on sf.net again and work there... (then we would also have the bug-tracker back in the same place) At the moment I see just 2 drawbacks: I don't know why you would ever do that, sf.net pretty much sucks. 1.) not hosted by mediawiki (really a drawback?) 2.) no review (this is the one and only advantage of git till now, and in fact it's git-review which causes issues too) The list of advantages on the other side, is that long that I will not even start making one, think of it yourself and please give me some feedback! At least I do not see if there will ever be a point in time when GIT will start to work as well as SVN did in the past. I do also not see why I have to enter 5 commands just to make a simple commit. And that will never change... Thanks for your thoughts and Greetings DrTrigon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIGBzQACgkQAXWvBxzBrDC40gCeNt8b7KoBLV9BDNDojjM01Upp ZsEAoIQIJ7W1FGMNysOE7LIp4qi25pyW =mvrX -END PGP SIGNATURE- --Legoktm ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Pywikibot, GIT and TS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.08.2013 12:37, legoktm wrote: On Sat, Aug 10, 2013 at 5:26 PM, Dr. Trigon dr.tri...@surfeu.ch mailto:dr.tri...@surfeu.ch wrote: Hello all! Pywikibot finished GIT migration. Now a question has anybody ever tryed to clone and use the e.g. the pywikibot/compat repo on the TS? If I do, I get and .git folder of about 200MB which nearly fills my home quota. (this is the plain clone - nothing done to/with it yet!!) If you read the instructions (https://www.mediawiki.org/wiki/Manual:Pywikipediabot/Gerrit), it recommends you only clone with a --depth of 3 (or anything smaller), and it will take up very little space. Yes of course there is a solution - but it again one thing that can go wrong and another paramter you have to remeber and use. By the way it would be a good thing if it would be possible to develop from TS also. And then all the 200MB are needed, aren't they? Yes I could do 'git gc' I could also switch to using SVN from github (but needs to handle all externals manually)... So... what was acutally the reason for switching to GIT? Despite the fact that I have to enter about 1 million different commands now (in SVN I needed 5 ... maybe 10 - 1 command per action, in GIT I need about 5-10 command PER action) I am dealing 75% of my time with GIT issues (that SVN did not have)... I don't follow. git commit filename.py, git review -R, and then hit +2. As mentioned on mediawiki you should in fact first create a branch. And I don't thinkg that just +2 all your own commits makes sense, becuase then we weould not have to use git review at all and could just push the stuff. In fact I am not able to to USE or further develop the GIT repo since the migration - and I am SERIOUSLY thinking about setting up an own copy on sf.net http://sf.net again and work there... (then we would also have the bug-tracker back in the same place) At the moment I see just 2 drawbacks: I don't know why you would ever do that, sf.net http://sf.net pretty much sucks. Yes, but git sucks too. At the moment I CAN work with svn (and sf.net but alternatives are very welcome) but I have to use A LOT OF WORK-A-ROUNDS to do so with git. It's all about work-load; all the migrations, changes and stuff taking place at the moment just stops me of doing my work. I should bug fix and develop bots for wikidata and commons, instead I have to migrate to Labs and GIT. And as it looks like git will - even if it works perfectly - just increase workload compared to svn. Greetings DrTrigon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIGHoUACgkQAXWvBxzBrDCrmgCgqhS8NcgDCiZLTMGj/74a96N5 IaEAniD5M4fZDufqSM/SDcb+srsbKkZI =ntr8 -END PGP SIGNATURE- ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Pywikibot, GIT and TS
(anonymous) wrote: [...] It's all about work-load; all the migrations, changes and stuff taking place at the moment just stops me of doing my work. I should bug fix and develop bots for wikidata and commons, instead I have to migrate to Labs and GIT. And as it looks like git will - even if it works perfectly - just increase workload compared to svn. You could try not to cause unnecessary workload for others by confining Pywikipediabot questions to its dedicated mail- ing list. If you need additional storage on the Toolserver (for what- ever reason), please file an issue in JIRA. Tim ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
