[implementations-list] When and how to check code into SVN (was: text objects)
On Wed, Jun 24, 2009 at 2:56 PM, Alessandro Piras <[email protected]> wrote:
I will switch to version 0.3.0 when I'll get repeatable visual commands XD I'm also thinking about improving visual block mode, and refactor the code a little ^^ Actually, I'm already working on a multiple file version, I split the code into several files hat should contain more or less separate functionalities, as navigating thru a big file usually bothers me quite a lot, especially when there are huge functions like the redefinition of viper-prefix-arg-com. Anyway, it's still possible to redistribute vimpulse as one big file, and there's a ready Makefile that does the job. What do you think? better to upload the split file version now or when I'm done with the visual command repetition stuff?
It doesn't matter when you check the split file version into SVN. But it's best if the splitting checkin doesn't involve any code changes; make all code changes in a separate checkin. By the way, have you been bumping the version number and making a new release on EmacsWiki every time you checked in code? You don't have to. You can make a release just every few weeks or so. Also, it's possible to set things up so that a mail goes to the mailing list every time you make an SVN checkin. BTW I like that the version vimpulse.el on EmacsWiki is one big file I can simply download and install :) Cheers, -Jason
ok, I'll check in the split file version now then, before changing the code. There are some changes in the code though, in that I sorted the functions, and reformatted some comments. Also, each file has a (provide 'something) statement. But as I said, producing the whole-file version is very easy, it's just one cat command I put in a Makefile, just for the sake of EmacsWiki. About the releases on EmacsWiki, yeah, maybe I can go slower there.. But I was very eager to let people try the new stuff, and get their bug fixed :) 2009/6/24 Jason Spiro <[email protected]>
On Wed, Jun 24, 2009 at 2:56 PM, Alessandro Piras <[email protected]> wrote:
I will switch to version 0.3.0 when I'll get repeatable visual commands XD I'm also thinking about improving visual block mode, and refactor the code a little ^^ Actually, I'm already working on a multiple file version, I split the code into several files hat should contain more or less separate functionalities, as navigating thru a big file usually bothers me quite a lot, especially when there are huge functions like the redefinition of viper-prefix-arg-com. Anyway, it's still possible to redistribute vimpulse as one big file, and there's a ready Makefile that does the job. What do you think? better to upload the split file version now or when I'm done with the visual command repetition stuff?
It doesn't matter when you check the split file version into SVN. But it's best if the splitting checkin doesn't involve any code changes; make all code changes in a separate checkin.
By the way, have you been bumping the version number and making a new release on EmacsWiki every time you checked in code? You don't have to. You can make a release just every few weeks or so. Also, it's possible to set things up so that a mail goes to the mailing list every time you make an SVN checkin.
BTW I like that the version vimpulse.el on EmacsWiki is one big file I can simply download and install :)
Cheers, -Jason
_______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
On Wed, Jun 24, 2009 at 4:30 PM, Alessandro Piras <[email protected]> wrote:
ok, I'll check in the split file version now then, before changing the code.
There are some changes in the code though, in that I sorted the functions, and reformatted some comments. Also, each file has a (provide 'something) statement. But as I said, producing the whole-file version is very easy, it's just one cat command I put in a Makefile, just for the sake of EmacsWiki. About the releases on EmacsWiki, yeah, maybe I can go slower there.. But I was very eager to let people try the new stuff, and get their bug fixed :)
Those people who want the latest version can check it out from SVN. :) But you also can make releases as often as you want -- even one release five minutes after another. It's not wrong -- it's just more effort.
participants (2)
-
Alessandro Piras -
Jason Spiro