Pike-devel October 2010

pike-devel@lists.lysator.liu.se

5 participants
10 discussions

Ignoring config.h.in
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 29 Oct '10

29 Oct '10

Git status bothers me about untracked files: # Untracked files: # (use "git add <file>..." to include in what will be committed) # # src/modules/Gz/zlib_machine.h.in # src/modules/Pipe/config.h.in # src/modules/SANE/config.h.in # src/modules/_Image_GIF/config.h.in # src/modules/_Image_JPEG/config.h.in # src/modules/_Image_TIFF/config.h.in # src/modules/_Image_XFace/config.h.in # src/modules/_Regexp_PCRE/pcre_machine.h.in # src/post_modules/_ADT/config.h.in # src/post_modules/_Image_SVG/config.h.in Turns out that the patterns for these files in .gitignore have trailing whitespace, something cvs apparently ignored but git does not. It'd be nice if the conversion had taken care of this, but I guess the only option now is to correct the patterns at the branch heads?

5 21

Outage for CodeLibrarian
by Peter Bortas ＠ Pike developers forum 25 Oct '10

25 Oct '10

I'm tracking down some bugs in the live installation of Librarian, so it might go up and down a bit for the next hour.

2 2

inotify
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 25 Oct '10

25 Oct '10

>hope you returned home well. I remember us talking about that you have a >file notification module somewhere that you wanted to commit into 7.9. As >i still have my inotify stuff lying around, do you think you can make >your code available somewhere in some git so that i can have a look and >possibly merge (if there is something to merge). I'll have to clear it with Roxen first, since it's part of the product. BTW: It seems inotify is on the way to being obsoleted by fanotify. BTW2: I just performed some comparisons of Pike's default string hashing function (aka DO_HASHMEM()) with CRC32, and the variance difference to a perfect hash function for the both are comparable, with CRC32 consistently being somewhat better. ZERO below is the pessimal hashfunction that returns zero for all strings. Hashfunction: DO_HASHMEM CRC32 ZERO Hilfe: 0.0368884 0.0359854 2.67415 GTK1: 0.0319663 0.0301390 1.90823 GTK2: 0.0320599 0.0305676 1.96876 Shuffler: 0.0496259 0.0475051 2.42460

3 3

Merge vs rebase policy
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 24 Oct '10

24 Oct '10

Shall we try to decide on a policy for merging vs rebasing? Personally I prefer simple linear histories. That makes it easy to follow the log, and it simplifies bisecting. Iow, the default would be to use "rebase = true" in tracking branches. Branches and merges still have their place, but imo they're better suited for more long-lived topic branches.

5 12

"Corrected" shell quoting
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 12 Oct '10

12 Oct '10

821fbe3a seems to have broken compilation on Solaris: sh: syntax error at line 1: `(' unexpected *** Error code 2 The following command caused the error: MAKE="`if [ "xmake" = "x" ]; then echo "${MAKE-make}"; else echo "make"; fi`" export MAKE && "${MAKE}" `$MAKE force --no-print-directory >/dev/null 2>&1 && echo --no-print-directory || :` "MAKE=${MAKE}" "CONFIGUREARGS=" "BUILDDIR=build/${PIKE_BUILD_OS:-`uname -s -r -m|sed "s/ /-/g"|tr "[A-Z]" "[a-z]"|tr "/()" "___"`}" METATARGET= _make_in_builddir Frankly I don't understand the change; the double quotes inside the backquotes need to be escaped, otherwise they end the double-quoted string which starts with "BUILDDIR=... Different quotes do not nest in sh, when a startquote is found the matching end quote is looked for using only the rules which applies to the start quote. So to have "s inside a double-quoted string (which also happens to contain a couple of backquotes), they need to be escaped.

2 3

merges in git
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 11 Oct '10

11 Oct '10

Hm, maybe any branch which does not have "/" in its name could be considered a "main branch"?

3 3

merges in git
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 11 Oct '10

11 Oct '10

But since "/" is already used in branch names in the new pike repo, a different separator char is probably better. ":", perhaps.

1 0

merges in git
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 11 Oct '10

11 Oct '10

Looking at the pike-librarian for last friday, I see .gitignore being fixed for the whitespace problem in 8 branches. So I would have expected to see 8 commits. But instead I see a 8 commits, and 14 merges. This looks cluttered and bizarre to me. Why weren't the fixes simply done on one branch and then cherry-picked to the others, instead of this self-indulging juggling with merges?

3 4

Reminder: Pike Conference in Berlin in 2 weeks
by Bill Welliver 05 Oct '10

05 Oct '10

Sorry for any potential duplication of recipients... This is just a friendly reminder about the rapidly approaching conference in Berlin, 18-19 October. I'm told that there have been some registrations, but oddly (sadly?), none from the Pike homeland of Sweden. I hope the short notice hasn't prevented too many folks from attending; it's always interesting to catch up and hear about all of the latest pike projects face-to-face, even if it's just a day. I know I'll be in town from Sunday afternoon through Wednesday afternoon, as will a few others. For more information, or to register, please drop my the conference website at: http://pike2010.webhaven.eu As always, please don't hesitate to drop me a note with any questions or comments (though I'm not part of the "conference management committee"). Hope to see you in Berlin, Bill

1 0

Switching to git and 7.9 news
by Peter Bortas 05 Oct '10

05 Oct '10

Good news everyone! At long last grubba has returned from his excursions into the land of commit graph archeology and brings back with him the complete and unified Pike history in one git repository. Marcus has been sacrificing copious amounts of defenceless computrons on the operation of verifying that the completed repository looks correct and has now provided his seal of approval. The switch from CVS to git is thus now completed. The instructions for cloning your very own copy of the pike repository are available here: http://pike.ida.liu.se/development/git/rw-git.xml To avoid the wrath of your fellow developers, please read the instructions carefully, and get a new enough git binary before checking out! In other news, Pike 7.9 is now open for commits and is the default branch. Enjoy! -- Peter Bortas

4 15

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