Repository with 80 tags?), and just tighter. More portable, it’s a hell of a lot faster (ever tried to check out a Subversion History, branches, tags, merges, and everything else, all in one package. It’s just so much more sane to get a project repository, with all of the That means where things go is completely ad-hoc, or convention-driven at best.Īnd god forbid if you decide to change the convention and move stuff around! Repository, I now realize, is really very much like a versioned file system. Hell of a lot more often, just because it’s so easy, the history remains intact,Īnd everything just stays more up-to-date and closely integrated.īut I also really appreciate the project-based emphasis of Git. I no longer will have to think about what revisions to include in a merge, orĬreate a branch just to “tag” a merge. Hell, probably closed-source, too, for that matter. Highlighted just how much better a fit Git is for the way in which we do Open Not because it wasĭifficult (it was) and required a number of hacks (it did), but because it I also just wanted to say that the process of reconstructing the merge historyįrom CVS and Subversion was quite an eye-opener for me. Corrections and comments would be greatly appreciated. If you’re familiar with the “Git way,” I would greatly appreciate your feedback ![]() Creating a Release, in which the fine art of branching, tagging, and.Contributing via Email, for those who don’t want a GitHub account (needs.Starting a Project Branch, which you’d need to read if you were taking onĪ major development task, such as a Summer of Code project.Merging with Git, to cover the frequent merging from Bricolage maintenanceīranches into master, and how to get said merges pushed upstream.Working with Branches, describing how to track a maintenance branch in.Contributing a Bug Fix, an intro to the Git way of doing things (as far as.Working with Git, explaining how to get set up with a forked Bricolage.To my fellow Bricoleurs how to start hacking. Week, today I completed writing up a set of GitHub wiki documents explaining Just a quick followup on the completion of the Bricolage Git migration last Looking for the comments? Try the old layout. Less right to maintain, given that I haven’t used CVS in years. Notification script from which SVN::Notify was derived - and which I have even PS: Would love it if someone also could take over activitymail, the CVS On this post, or me on Twitter, or send an email. ![]() Take over maintenance, make it even better, please get in touch. Therefore, SVN::Notify is formally up for adoption. Nevertheless, thereĬertainly could be some things that folks want to add, like TLS support, Relatively stable, with few bug reports or complaints. This has probablyīeen my most popular modules, and I know that it’s used a lot. It no longer seems appropriate that I maintain SVN::Notify. As such, I no longer use Subversion in my day-to-day work. The server I’ve used for all my services, including Subversion, so I’ve moved Support company, Kineticode, for many years. I’ve kept my various Perl modules in a Subversion server run by my Bricolage
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |