Pike-devel March 2008

pike-devel@lists.lysator.liu.se

7 participants
15 discussions

Git 101 revised for pikers
by Stephen R. van den Berg 18 Mar '08

18 Mar '08

A.S. After toying with git some more, I revised the recommended instructions to follow the mirror(s) apt-get install git-core git clone git://git.cuci.nl/pike cd pike git gc git branch -r # List available active remote branches # dead branches are available as # tags (like: 7.5 or ulpc.old) git checkout -f origin/7.7 git branch -f master # This creates your own development # branch called "master" # tracking official version 7.7 git checkout -f master git log master git log origin/7.7 git log origin/7.6 git log origin/7.4 Now edit around, and commit changes using: git commit -a -m "Some useful one-line-description" and repeat as often as needed (of course). In order to update the mirror from upstream (my repository, where you cloned from), simply run: git fetch every once in a while. After doing so, perform: git rebase origin/7.7 to actually move forward your own "master"-branch changes so they are automatically merged and (re)based onto the latest (official) updates from 7.7 Pushing back the changes into the official release involves using CVS (externally from git) still. The native git mechanisms cannot be used for that until the official repository is also changed to git. The nice thing about git is that merges from the developmentbranch back into older stable branches are seemless and fully annotated. These advantages however, cannot be used until git is used natively. In theory, the merges could be retro-fitted into the branches, but there currently is no automated way of doing that to the existing tree (it can be done manually, git allows all kinds of "afterward fixing"). ------------------------------------- For Roxen/Caudium/Chilimoon, try the above with: git clone git://git.cuci.nl/roxen git branch -r Then pick either: origin/5.0 # for Roxen development branch origin/caudium # for Caudium development branch origin/chilimoon # for Chilimoon development branch -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). "Good moaning!"

5 7

www.ohloh.net contributor list
by Stephen R. van den Berg 12 Mar '08

12 Mar '08

For a tiny bit of Pike promotion, and to show that the community is thriving, it might be a good show of hands to put actual accounts behind the contributor list of pike at the following page: http://www.ohloh.net/projects/7336/contributors Also, feel free to update the data on Pike there (or even Roxen/Caudium). The data they're using is the live git mirror I put up for the Pike repository (it tracks bleeding edge pike (7.7), at the moment). -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). "Good moaning!"

4 5

Re: www.ohloh.net contributor list
by H. William Welliver III 12 Mar '08

12 Mar '08

That appears to be the case; It says that caudium has a large percentage of Java code, and that Fins is written predominantly in JavaScript (which it isn't). The counts seem to be based on file extension, so perhaps we should rename all of our code with .php?? :) I find some of the metrics interesting, but there are a lot of flaws behind automated analysis. I wouldn't say that the site is solely designed to permit poaching of developers; but I've always been skeptical of the whole "social networking" thing, so I'm not sure I see the real benefits to putting a lot of effort into it. Bill > Are you sure? I find it hard to believe that 79% of the Roxen code > is written in XML... > > According to a quick wc -l, a fresh Roxen consists of the following: > > C 605 > css 172 > h 1111 > HTML 1987 > Java 4358 > js 1497 > Perl 478 > Pike 166017 > sh 2016 > VBS 78 > XML 49140 > > My guess is that it has just ignored the pike and pmod files.

1 0

Re: follow up: segfault
by Peter Bortas ＠ Pike developers forum 10 Mar '08

10 Mar '08

It's a tentative fix, so 7.7: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.7/src/in…

2 3

Java configure
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 05 Mar '08

05 Mar '08

Pike 7.6 detects that I have Java (-lzip -ljava -ljvm ), but 7.7 doesn't.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel March 2008