|
1904
|
1 2005-05-24.txt:20:22:17: <malaprop> So moving MySQL dumps around is bad, but a patch to the wiki that'll have to be maintained for all the versions is OK?
|
|
|
2 2005-05-24.txt:20:25:40: <kipple> in MoinMoin I think that if you rsync the entire directory hirearchy you would get all patches as well
|
|
|
3 2005-05-24.txt:22:03:48: <GregorR> Oh, just remembered. About patches for "Wiki!" - wouldn't we want the wiki software itself to rsync down with everything else, regardless of what software it is? I mean, all software has versions ...
|
|
|
4 2005-05-25.txt:00:54:37: <calamari> well, hopefully not, since rsync only sends the files that changed, right? or does it even do better than that and send a patch?
|
|
|
5 2005-05-25.txt:00:54:49: <kipple_> it sends a patch.
|
|
|
6 2005-05-25.txt:01:09:19: <calamari> the question is how much bandwidth would it take to prepare the patch vs just sending the zipped file?
|
|
|
7 2005-06-04.txt:00:02:09: <jix> automatic downloading+(patching if needed)+compilation of source code
|
|
|
8 2005-07-19.txt:23:18:24: <jix> the irc msg dispatcher is done 70%
|
|
|
9 2005-07-25.txt:01:38:58: <pgimeno> graue: could you please test if this patch for bff causes it to work? http://www.formauri.es/personal/pgimeno/temp/bff.patch
|
|
|
10 2005-07-25.txt:01:39:42: <pgimeno> at least the patch makes valgrind stop complaining
|
|
|
11 2005-07-25.txt:03:23:06: <graue> pgimeno: the patch didn't fix it
|
|
|
12 2005-07-25.txt:17:29:31: <pgimeno> jix: did you try with my patch?
|
|
|
13 2005-07-25.txt:17:30:30: <jix> pgimeno: patch?
|
|
|
14 2005-07-25.txt:17:31:08: <pgimeno> http://www.formauri.es/personal/pgimeno/temp/bff.patch - would you mind to try applying it and see if it works?
|
|
|
15 2005-07-26.txt:00:11:20: <pgimeno> graue: thanks for testing. Have you tried the patch which also replaces n with (n+1)?
|
|
|
16 2005-07-26.txt:00:17:15: <graue> no, I didn't know there was a new patch, where can I find it?
|
|
|
17 2005-07-26.txt:00:18:23: <pgimeno> it's in the same place, http://www.formauri.es/personal/pgimeno/temp/bff.patch
|
|
|
18 2005-09-06.txt:10:30:57: <graue> I think we need a "hide esoshell namespace edits" patch for the recent changes page
|
|
|
19 2005-10-21.txt:14:07:27: <fizzie> I am wondering if that thing would work better with the OpenTTD "new pathfinding" patch.
|
|
|
20 2005-11-10.txt:01:16:19: <calamari> doesn't patch cleanly
|
|
|
21 2005-11-24.txt:01:19:44: <fizzie> gcj --classpath ../jogl.jar:./swt.jar -findirect-dispatch -o jtest --main=jtest jtest.java ; export LD_LIBRARY_PATH=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre/lib/i386:.:../jogl-natives ; export CLASSPATH=../jogl.jar:./swt.jar ; ./jtest works.
|
|
|
22 2005-11-24.txt:14:41:48: <fizzie> I get the same UnsatisfiedLinkError when I "gcj -I jogl/build/jogl.jar -o jtest -lgij -findirect-dispatch jtest.java ; ./jtest -cp jogl/build/jogl.jar jtest", but it possibly-works when I manually set LD_LIBRARY_PATH=the-long-path-to-jawt.
|
|
|
23 2005-11-24.txt:14:51:40: <fizzie> I think gcj is supposed to set it automagically. There's some talk in http://gcc.gnu.org/ml/java-patches/2005-q3/msg00285.html
|
|
|
24 2005-11-24.txt:14:53:24: <fizzie> Here's about jawt: http://gcc.gnu.org/ml/java-patches/2005-q3/msg00295.html
|
|
|
25 2005-11-24.txt:14:57:31: <fizzie> Right, now it works, at least jikes-compiled and with /usr/lib/jvm/java-gcj/bin/java. The gcj-native-compiled (-lgij -findirect-dispatch blahblah) doesn't, but might after recompilation.
|
|
|
26 2005-11-24.txt:14:59:24: <fizzie> fis@colin:~/prog/java$ gcj -I jogl/build/jogl.jar -o jtest -lgij -findirect-dispatch jtest.java
|
|
|
27 2005-12-14.txt:11:41:12: <nooga> hehe, i've got nude patch for L2
|
|
|
28 2005-12-14.txt:11:41:30: <puzzlet> they make patch for everything
|
|
|
29 2005-12-14.txt:11:43:23: <handongseong> sometimes that kinds of patches worsen the gameplay... i once used no-mosaic patch for an adult game and it was truly horrible
|
|
|
30 2006-01-16.txt:11:34:01: <SimonRC> Grrr, Haskell professor sent out patch that doesn't actually correct the probel *at* *all*.
|
|
|
31 2006-01-16.txt:11:36:33: <SimonRC> fortunately I could see the proble with his patch for it immediately.
|
|
|
32 2006-02-06.txt:18:17:40: <GregorR> No offense, but please submit patches.
|
|
|
33 2006-02-06.txt:18:19:09: <GregorR> I guess asking for patches is a bit ridiculous, isn't it :-P
|
|
|
34 2006-02-12.txt:09:34:36: <GregorR> Please submit patches back so I can shuffle through them and get rid of the ones I don't like X-P
|
|
|
35 2006-04-09.txt:00:27:25: <calamari> should I submit a patch? lol
|
|
|
36 2006-04-23.txt:22:38:22: <Arrogant> Break it with a patch on Tuesday
|
|
|
37 2006-04-23.txt:22:38:31: <Arrogant> Apologize and revert with another patch on Wednesday
|
|
|
38 2006-04-28.txt:19:13:45: * SimonRC considers the unmaintainable buggy spagghetti code consisting entirely of patches that is our DNA, and decides God didn't do a very good design job.
|
|
|
39 2006-05-25.txt:07:20:57: <nooga> and then just dispatch i/o
|
|
|
40 2006-07-24.txt:01:28:08: <GregorR> Patches gladly accepted.
|
|
|
41 2006-07-25.txt:05:23:43: <pikhq> Of course I'd give you the patch.
|
|
|
42 2006-07-25.txt:21:13:29: <pikhq> !i 1 I think we should patch that a bit.
|
|
|
43 2006-07-25.txt:21:13:37: <EgoBot> I think we should patch that a bit.Blahk
|
|
|
44 2006-07-25.txt:21:19:38: <pgimeno> GregorR-W: btw, are you interested in a security patch for the malbolge interpreter?
|
|
|
45 2006-07-25.txt:21:25:33: <pgimeno> GregorR-W: http://www.formauri.es/personal/pgimeno/temp/malbolge.patch
|
|
|
46 2006-07-28.txt:04:11:30: <Razor-X> Now, how to use this ``patch'' thingamajigger....
|
|
|
47 2006-07-28.txt:04:12:00: <GregorR> What are you trying to patch?
|
|
|
48 2006-07-28.txt:04:12:30: <Razor-X> While I just added in 7 lines... I thought you may want the patch I made :P.
|
|
|
49 2006-07-28.txt:04:12:45: <GregorR> If you want to make a patch, you're not using the right program ;)
|
|
|
50 2006-07-28.txt:04:13:08: <GregorR> diff makes patches that patch installs.
|
|
|
51 2006-07-28.txt:04:22:24: <GregorR> No, doing too many things to patch it right now.
|
|
|
52 2006-07-28.txt:06:56:56: <Razor-X> Did you merge my ``patch'' in?
|
|
|
53 2006-07-29.txt:20:46:21: <pgimeno> reminder for Read-only Gregor: http://www.formauri.es/personal/pgimeno/temp/malbolge.patch
|
|
|
54 2006-07-29.txt:20:49:50: <Razor-X> .... A Malbolge patch?!
|
|
|
55 2006-07-29.txt:21:06:54: <Razor-X> T3h patch is almost finished for Bitwise operations.
|
|
|
56 2006-07-29.txt:21:19:16: <Razor-X> Yeah, I had ta be away-ish. Now I'm not. And it seems my patch works so far. Just two more things to add.
|
|
|
57 2006-07-29.txt:21:35:07: <pgimeno> seems that the patch is effective
|
|
|
58 2006-07-30.txt:01:37:20: <Razor-X> GregorR: Did you get my patch earlier?
|
|
|
59 2006-07-30.txt:08:07:31: <Razor-X> I wonder if GregorR added in my newest patch.
|
|
|
60 2006-07-30.txt:21:42:21: <Razor-X> Hmm... I wonder if GregorR added in my patches...
|
|
|
61 2006-07-31.txt:05:10:20: <Razor-X> Great patch idea.
|
|
|
62 2006-07-31.txt:21:05:08: <pikhq> (he patched it so !ps and !kill would still work if the rest of the bot shut down)
|
|
|
63 2006-08-01.txt:16:39:38: <pikhq> We'll patch Qemu to get it done right. >:D
|
|
|
64 2006-08-02.txt:07:42:57: <Razor-X> I write in Esolangs, and if an idea strikes me I patch Glass.
|
|
|
65 2006-08-08.txt:16:43:10: * pikhq makes his patches to dimensifuck.py GPLed.
|
|
|
66 2006-08-20.txt:02:56:53: <RodgerTheGreat> I seem to remember a case with a strain that could infect algal cells whose chloroplasts had been damaged by UV-radiation of some kind. they would apply "patch" code that could rebuild the affected proteins before making use of the cell.
|
|
|
67 2006-08-20.txt:03:00:08: <RodgerTheGreat> in fact, retroviruses are often used by genetic engineers as an easy way to patch existing organisms.
|
|
|
68 2006-08-20.txt:03:02:45: <CakeProphet> We could patch all sorts of problems that way
|
|
|
69 2006-08-20.txt:03:04:37: <RodgerTheGreat> if it's a retrovirus, you just patched the prokaryotes with new DNA. If it's a normal phage or something, the infected hosts will spawn fully-formed viruses with their normal protein coat, which can then reproduce without help.
|
|
|
70 2006-08-31.txt:23:23:13: <ihope> "The Windows honeypot is an unpatched version of Windows 2000 or Windows XP. This system is thus very vulnerable to attacks and normally it takes only a couple of minutes before it is successfully compromised."
|
|
|
71 2006-09-10.txt:01:51:37: <pikhq> calamari: We should patch mplayer to handle Brainfuck Audio directly. :p
|
|
|
72 2006-09-16.txt:21:51:30: <pikhq> Razor-X: Also, realise that Slackware just gives you a plain, unpatched kernel. . .
|
|
|
73 2006-09-16.txt:21:52:18: <Razor-X> It's stock unpatched, but it's an ancient version compiled without such overly modern things as USB support.
|
|
|
74 2006-09-22.txt:21:41:40: <fizzie> Don't see any news as to what happened with the SoC projects. Or any news at all after May 2nd. (Back when cras was still writing irssi, at least one could get bugs fixed by privmsging patches; with this new dev-team I don't have that luxury, since I don't feel comfortable talking to strangers.)
|
|
|
75 2006-09-25.txt:01:19:28: <pikhq> ALSA, after all, was originally just some additional 2.4 modules (xor 2.4 patch). ;)
|
|
|
76 2006-10-13.txt:01:12:32: <Razor-X> Pfft. Fine. I'll patch it myself then :P
|
|
|
77 2006-10-14.txt:01:09:37: <GregorR-L> FYI, I will accept any and all patches implementing PESOIX into EgoBF :P
|
|
|
78 2006-10-14.txt:03:34:54: <GregorR-L> But EgoBot is OSS - if somebody makes a patch, I'll accept it.
|
|
|
79 2006-10-26.txt:23:56:41: <pikhq> IMO, we should start with a very, very simple kernel (perhaps a patched linux-tiny) and a Brainfuck interpreter. . .
|
|
|
80 2006-10-27.txt:22:07:24: <SimonRC> hehehe: http://www.miranda.org/~jkominek/rot13/ssh-1.2.27-rot13.patch
|
|
|
81 2006-10-29.txt:18:40:26: * ihope continues patching up the interpreter
|
|
|
82 2006-11-19.txt:22:26:34: <SimonRC> A high-level router might only consider the first 8 bits, and dispatch based on those...
|
|
|
83 2006-12-06.txt:23:50:15: <SimonRC> encapsulation should be done with modules, datatypes should be defined seperately from their methods, multiple dispatch/overriding/virtual methods should be done with multimethods (and multiple-parameter typeclasses preferrably).
|
|
|
84 2006-12-20.txt:20:26:24: <Sukoshi> ....Which is a little late, since I've already made some really big patches.
|
|
|
85 2006-12-24.txt:01:43:41: <pikhq> GregorR: A patch is coming your way.
|
|
|
86 2006-12-24.txt:02:56:54: <oerjan> when you get to ], you use that global pointer to compile the ] _and_ to patch the corresponding [, finally letting the new global pointer be the previous content of the [
|
|
|
87 2006-12-27.txt:23:45:59: <Sukoshi> The mmap patch I recently committed sped it up, but we still need more optimizations.
|
|
|
88 2006-12-31.txt:00:43:57: <RodgerTheGreat_> CakeProphet: it's the best way to do it. In modern operating systems, executables contain absolute addresses which are patched to appropriate values based on where they're loaded as they're loaded into memory
|
|
|
89 2006-12-31.txt:00:46:29: <RodgerTheGreat_> that's really no different than a runtime patch. There's no need to store data in a clumsy way (strings) when we can do it in an efficient way (addresses). Absolute addresses are more complex to code with, but that's the *entire* point of having a compiler in the first place.
|
|
|
90 2006-12-31.txt:20:05:37: <pikhq> bsmntbombdood: The patch is in; he just needs to make a new tarball.
|
|
|
91 2007-03-19.txt:22:43:01: <bsmnt_bot> .h', 'pystate.h', 'object.h', 'patchlevel.h', 'setobject.h', 'intobject.h', 'intrcheck.h', 'objimpl.h', 'pystrtod.h', 'abstract.h', 'frameobject.h', 'complexobject.h', 'errcode.h', 'import.h', 'unicodeobject.h', 'pyport.h', 'sysmodule.h', 'fileobject.h', 'iterobject.h', 'ceval.h', 'funcobject.h', 'modsupport.h', 'listobject.h', 'moduleobject.h', 'longintrepr.h']
|
|
|
92 2007-04-01.txt:02:52:27: <Figs_> (patching the language)
|
|
|
93 2007-04-10.txt:23:54:33: <oerjan> essentially runtime type information. since this is multiple dispatch, the class struct doesn't contain enough information.
|
|
|
94 2007-04-14.txt:01:36:59: <SevenInchBread> basically just like.... talking to the MMU and dispatching interupts... and maybe some other stuff.
|
|
|
95 2007-04-14.txt:18:36:34: <SevenInchBread> the basic kernel should basically just... take hardware interupts and place them on a queue that can be accessed by like... a hardware-dispatch process of some kind
|
|
|
96 2007-05-05.txt:04:59:05: <GregorR> In a handy patch bundle.
|
|
|
97 2007-05-05.txt:23:29:14: <Pikhq> GregorR: I'm going to take a guess that you're not going to look at my patch at all. XD
|
|
|
98 2007-05-06.txt:03:37:24: * Pikhq is going to force GregorR to read that patch one of these days. . .
|
|
|
99 2007-05-06.txt:20:35:10: <GregorR> ~pikhq/pikhq_patch2.bundle doesn't exist.
|
|
|
100 2007-05-07.txt:21:30:06: <Pikhq> One of the cracks out there is a patched firmware for the Xbox 360 HD-DVD drive, allowing one to obtain those unreadable bits. ..
|
|
|
101 2007-05-18.txt:02:35:46: <Pikhq> Realising, of course, that you've already *got* a genetic algorithm for such generation in your HD; it's just a matter of patching it to not do I/O. . .
|
|
|
102 2007-05-24.txt:22:43:09: <SimonRC> heck, you can even change the multiple-dispatch mechanism without re-entering the methods.
|
|
|
103 2007-05-24.txt:22:43:31: <SimonRC> I realised I was dispatching on the first argument not the second, by accident, and I cahnged it and it just worked
|
|
|
104 2007-05-27.txt:03:27:22: <SimonRC> bsmntbombdood: quite possibly, but you'd have to backpatch it.
|
|
|
105 2007-06-07.txt:20:34:48: <SimonRC> but each rectangular patch of terrain must only connect to each other patch in one way, and never to itself, so some really twisted things can't be done.
|
|
|
106 2007-07-14.txt:06:53:34: <RodgerTheGreat> it's no different from the whitehats working to secure networks or patch memory leaks in firefox.
|
|
|
107 2007-07-17.txt:05:09:19: * pikhq runs off, feeling like patching Tcl's "if" statement. :p
|
|
|
108 2007-07-21.txt:00:54:32: <SimonRC> It is occasionally handy to be able to dispatch on return type
|
|
|
109 2007-07-23.txt:18:34:51: <SimonRC> you can build it on top of any OO system with a customisable dispatch policy
|
|
|
110 2007-07-28.txt:01:09:02: <ihope> If you have a patch of extremely salty water next to a patch of freshwater... how do you get energy out of that?
|
|
|
111 2007-07-28.txt:01:15:27: <RodgerTheGreat> and if the machine was interacting with it, it could strategically kill various algae colonies or patches via temperature control
|
|
|
112 2007-08-01.txt:15:00:32: <ehird`> he has nicely dispatched one hint, which has saved me from giving up
|
|
|
113 2007-08-05.txt:21:50:08: <SimonRC> in darcs, a source tree is just a set of patches applied to the empty tree
|
|
|
114 2007-08-06.txt:13:11:58: <ehird`> two people are still releasing patches for that under authorization for team17, you know
|
|
|
115 2007-08-18.txt:19:33:12: <pikhq> GregorR: All in favor of just patching the Plof spec?
|
|
|
116 2007-08-19.txt:20:37:54: <gwern> someone needs to patch NMajik - goldbach's conjecture is for even integers bigger than 2...
|
|
|
117 2007-08-19.txt:21:03:38: <zecrose> is there a patch for the bug?
|
|
|
118 2007-09-17.txt:02:53:11: <edwardk> so my apply/dispatch mechanism is uglier
|
|
|
119 2007-09-22.txt:00:46:26: <edwardk> its got a pattern match dispatcher, and primitive bigint support through GMP. assignment is primitive, beyond that most traditional language features, if, booleans, etc. are built up in the language
|
|
|
120 2007-09-29.txt:19:07:44: <pina> I've never really used C.. patches to the kernel and all, but I've never written anything from the ground up.. the code in that contest always stretches the neurons..
|
|
|
121 2007-10-03.txt:14:45:59: <RodgerTheGreat> plus, they ditched the gesture-driven task manager for a regular menu in the patch. :(
|
|
|
122 2007-10-18.txt:14:33:13: <ehird`> http://article.gmane.org/gmane.emacs.devel/80956 Emacs now edits videos. Millions of nerds patch GRUB support for it, set it as OS.
|
|
|
123 2007-10-26.txt:04:45:34: <RodgerTheGreat> Maybe it's more difficult to defrag recent memories *without* causing dreams as a side-effect, so the mechanisms that usually cause people to forget dreams act as some kind of patch to that behavior?
|
|
|
124 2007-11-05.txt:15:51:29: * Sgeo[Circe] is running r681 with a patch to prevent checking the version..
|
|
|
125 2007-11-05.txt:16:50:45: * Sgeo needed to patch a file to get Circe to work because of that..
|
|
|
126 2007-11-14.txt:19:24:56: <ehird`> (Amusing aside: jailbreakme actually patches up the tiff exploit after using it to do its thing)
|
|
|
127 2007-11-20.txt:22:32:47: <ehird`> random, esoteric and computer-related (although not programming-language-related) idea: is there a language-sensitive diff? you could get patches that don't die horribly with two different formattings (code-style that is) of the same source, etc.
|
|
|
128 2007-11-24.txt:16:21:40: <Figs> Is "multiple dispatch" really any different than overloading on C-style functions?
|
|
|
129 2007-12-30.txt:04:27:42: <pikhq> I may need to do some special patching of PEBBLE to make LNUM *convenient*. . .
|
|
|
130 2007-12-30.txt:06:45:52: <Sgeo> Implementation agenda: output w/ 0x00 0x00, then class Domain, then domain dispatcher
|
|
|
131 2007-12-30.txt:19:34:41: <ehird`_> Copying patch 238 of 1251...
|
|
|
132 2007-12-30.txt:21:23:02: <ehird`_> i need some kind of parse-dispatcher
|
|
|
133 2008-01-10.txt:16:05:55: <faxlore> how do you do dispatch?
|
|
|
134 2008-01-12.txt:17:31:54: <RodgerTheGreat> I dunno, english has adapted to all kinds of syntactic patches and markup pretty well
|
|
|
135 2008-01-15.txt:02:17:43: <ehird`> and therefore generic functions can dispatch on them
|
|
|
136 2008-01-15.txt:20:17:58: <ehird`> have one dispatcher function, underload()
|
|
|
137 2008-01-15.txt:22:32:46: <GreaseMonkey> #2 0x08048c1e in dispatch (o=0x804b058) at poop.c:223
|
|
|
138 2008-01-15.txt:22:32:46: <GreaseMonkey> #3 0x08048bd0 in dispatch (o=0x0) at poop.c:207
|
|
|
139 2008-01-21.txt:15:56:39: <ehird`> too many patches though
|
|
|
140 2008-01-21.txt:17:31:31: <ehird> but it's not fun.. you have to patch it to hell
|
|
|
141 2008-01-21.txt:17:33:04: <ehird> have a patch
|
|
|
142 2008-01-21.txt:17:33:05: <ehird> http://www.khaitu.com/public/kdelibs.patch
|
|
|
143 2008-01-23.txt:17:31:13: <ehird> - it's interactive: when your record a patch it asks which changes you want to record
|
|
|
144 2008-01-23.txt:17:36:41: <olsner> I've heard of e-mail services with GPG-based authentification of patches
|
|
|
145 2008-01-23.txt:18:12:28: <ehird> and the whole program is a switch statement dispatching on blimp numbers
|
|
|
146 2008-01-28.txt:17:48:32: <ais523> I've pushed 5 patches at you
|
|
|
147 2008-02-12.txt:21:39:54: <ehird> dispatch the stormtroopers
|
|
|
148 2008-02-18.txt:20:28:37: <ehird`> and monkeypatches it
|
|
|
149 2008-02-20.txt:18:32:02: <ehird`> oerjan: well, mostly it means you'd patch the code
|
|
|
150 2008-02-23.txt:01:35:21: <ehird> Someone should submit a patch to gnu coreutils, replacing true.c with:
|
|
|
151 2008-03-06.txt:22:01:14: <AnMaster> ehird, feel free to make patches to my code!
|
|
|
152 2008-03-10.txt:20:25:51: <AnMaster> send me a patch for ccbi when you fixed it
|
|
|
153 2008-03-11.txt:18:17:41: <lament> i understand the issues with multiple dispatch
|
|
|
154 2008-03-12.txt:22:01:04: <AnMaster> ais523_non-admin, and you can do that on linux with some hardening kernel patchsets
|
|
|
155 2008-03-19.txt:13:51:01: <Deewiant> The original Befunge-93 language implementation was developed by a small but dedicated user base; the result was Befunge-96 (with concurrency), and then Befunge-97, which added a batch of new features. By 1998, a new language was born: Funge-98, which took Befunge out of two dimensions and into Hilbert space. Development of Befunge-100 (presumably the victim of an un-patched Y2K bug) allegedly continues.
|
|
|
156 2008-03-20.txt:15:58:52: <Deewiant> AnMaster: and did you apply the patches from the page
|
|
|
157 2008-03-20.txt:16:15:27: <AnMaster> <Deewiant> AnMaster: and did you apply the patches from the page
|
|
|
158 2008-03-20.txt:16:20:43: <Deewiant> AnMaster: fixed the patch links, cheers
|
|
|
159 2008-03-29.txt:00:57:37: <marshmallows> so you just pass in a dispatch table with options
|
|
|
160 2008-03-29.txt:16:06:18: <Deewiant> ehird: I don't like Darcs's patch-based model
|
|
|
161 2008-03-31.txt:15:19:11: <AnMaster> patches are welcome of course
|
|
|
162 2008-03-31.txt:16:11:43: <ehird> & is based on a Theory of Patches written by a physicist
|
|
|
163 2008-03-31.txt:16:18:50: <ehird> letting people submit patches is built in--
|
|
|
164 2008-03-31.txt:17:09:56: <ehird> Also, when e.g. patches are released I'd probably make a pre-patched version for convenience
|
|
|
165 2008-03-31.txt:17:11:36: <ais523> and the Debian repos host the original, and a patch to Debianise it
|
|
|
166 2008-03-31.txt:17:13:02: <ehird> By the way, patch(1) doesn't like your patch
|
|
|
167 2008-03-31.txt:17:14:39: <ais523> but the patch has Unix newlines
|
|
|
168 2008-03-31.txt:17:14:43: <ais523> and that's enough to confuse patch
|
|
|
169 2008-03-31.txt:17:15:52: <ehird> patching file src/idiotism.oil
|
|
|
170 2008-03-31.txt:17:16:22: <ais523> ehird: OTOH, unlike the Debian maintainer, you wouldn't be too scared to merge the patch by hand, right?
|
|
|
171 2008-03-31.txt:17:17:59: <ehird> Gosh, patch is such an arcane format
|
|
|
172 2008-03-31.txt:17:19:08: <ais523> in fact, that's the reason that the patch is confused like that
|
|
|
173 2008-03-31.txt:17:20:58: <ais523> (Joris Huizer, who has contributed so many patches to C-INTERCAL recently that there's a Joris-specific changelog section, sent a few OIL corrections in, but confessed to not really understanding the syntax)
|
|
|
174 2008-03-31.txt:17:52:48: <AnMaster> but not TRDS and CONT, sure if someone makes a patch
|
|
|
175 2008-04-01.txt:20:23:34: <AnMaster> ais523, hope you can make a patch soon
|
|
|
176 2008-04-01.txt:20:30:58: <ais523> AnMaster: but that seems reasonable based on what the patch does
|
|
|
177 2008-04-01.txt:20:39:34: <ais523> ehird: I patched my version of unlambda.i because it had an error on line 323
|
|
|
178 2008-04-01.txt:21:20:48: <AnMaster> oh and any patches will not be accepted in the current coding style of ick ;P
|
|
|
179 2008-04-01.txt:22:40:49: <ais523> ehird: Joris Huizer has sent me a lot of patches
|
|
|
180 2008-04-03.txt:04:17:25: <GregorR> Oh, I uploaded the binutils/gcc/newlib patches too.
|
|
|
181 2008-04-03.txt:12:25:19: <AnMaster> ais523, well if you make a patch and send it upstream?
|
|
|
182 2008-04-03.txt:12:25:42: <ais523> if you can somehow get the patch accepted
|
|
|
183 2008-04-03.txt:12:26:00: <AnMaster> ais523, well no, just "look at included makefiles" patch
|
|
|
184 2008-04-03.txt:14:11:31: <AnMaster> ais523, oh and patches are welcome as long as they are not intercal interface specific and 1) follow current coding style 2) gives no new valgrind error 3) works fine both with boehm-gc and without
|
|
|
185 2008-04-03.txt:18:06:56: <lament> because it's up to the object to dispatch on the messages
|
|
|
186 2008-04-03.txt:18:07:49: <lament> so the dispatch happens at runtime at the discretion of the object
|
|
|
187 2008-04-03.txt:18:10:27: <lament> CakeProphet: with dynamic typing it is still not clear who performs the dispatch
|
|
|
188 2008-04-04.txt:11:58:09: <fizzie> There was a printf patch on the mingw mailing list which made it automagically convert %..ll to %..I64 on Windows, but I couldn't find out whether they actually applied it.
|
|
|
189 2008-04-04.txt:14:59:24: <AnMaster> system. Patches are welcome if they don't mess up source too much (anything
|
|
|
190 2008-04-04.txt:20:59:44: <SimonRC> dynamic dispatch can only be done on the "first argument" to a method, *and* all methods must be declared in the class of their "first argument" <-- killer combo
|
|
|
191 2008-04-05.txt:05:06:56: <RodgerTheGreat> maybe I'll submit one of my old paintings, "Hunter of Spatulas" http://www.nonlogic.org/dump/images/1207368367-spatch.jpg
|
|
|
192 2008-04-06.txt:22:14:10: <GregorR> http://www.codu.org/jsmips/patches/
|
|
|
193 2008-04-09.txt:18:39:50: <ehird> oklopol: basically, in 'x.y(z)' you dispatch on the magic first param - self, here x
|
|
|
194 2008-04-09.txt:18:39:50: <ehird> oklopol: with generic methods you dispatch on THEM ALL
|
|
|
195 2008-04-09.txt:18:40:19: <ehird> and also removes the arbitary 'dispatch only on first magic param thing'
|
|
|
196 2008-04-09.txt:18:48:36: <oklopol> anyway, ehird: it doesn't make the code less complicated to have + dispatch on its arguments
|
|
|
197 2008-04-10.txt:00:11:26: <oklofok> the dispatch is just plain oklotalk logic
|
|
|
198 2008-04-10.txt:00:49:50: <oklofok> you can't dispatch on anything except what the object matches on
|
|
|
199 2008-04-11.txt:18:07:21: <ais523> normally to say that I screwed up the patch I sent them again...
|
|
|
200 2008-04-11.txt:18:07:40: <ais523> for some reason, every patch I've sent to Debian has been missing, or misformatted, or had the wrong sort of newlines, or something like that
|
|
|
201 2008-04-11.txt:18:08:23: <ais523> because I had corrected the newlines in the file I was patching against and forgotten about it
|
|
|
202 2008-04-11.txt:23:35:11: <pikhq> GregorR: Patch to Egobot?
|
|
|
203 2008-04-11.txt:23:37:48: <ehird> So I'd only patch it if GregorR would put it up.
|
|
|
204 2008-04-11.txt:23:40:24: <pikhq> Just write the patch and hand it to Gregor.
|
|
|
205 2008-04-12.txt:00:33:02: <ehird> GregorR: Well, I have a patch if you want it
|
|
|
206 2008-04-12.txt:16:04:09: <ehird> and send you a patch
|
|
|
207 2008-04-12.txt:20:07:10: <ehird> GregorR: so about that egobot patch..
|
|
|
208 2008-04-17.txt:17:48:05: <ehird> i was just thinking, since a is what I dispatch on..
|
|
|
209 2008-04-17.txt:17:48:37: <oklopol> currently, the dispatching rules are very stupid, and i could just do (func arg arg)
|
|
|
210 2008-04-17.txt:17:50:17: <oklopol> it's nice, but i want the oklotakl dispatch rules...
|
|
|
211 2008-04-17.txt:17:55:18: <ehird> oklopol, because the first thing you try to dispatch on is the first arg right?
|
|
|
212 2008-04-17.txt:17:56:57: <oklopol> but the dispatch rules are really retarded.
|
|
|
213 2008-04-20.txt:10:45:34: <oklopol> if pattern matching fails, pattern-based dispatching can be done by calling functions with disjoin patterns with the arg
|
|
|
214 2008-04-21.txt:12:23:27: <ais523> I think it's something to do with the IE version or patchlevel, but I don't particularly care
|
|
|
215 2008-04-21.txt:12:52:33: <ais523> actually, I should probably send the patched development somewhere
|
|
|
216 2008-04-21.txt:13:05:28: <AnMaster> ais523, even if there are no *~, there could be other things, say *.orig from a patch or so on
|
|
|
217 2008-04-26.txt:23:16:43: <oklopol> so basically, receivers and functions are separate in that receivers are *objects*, they take a method name, the atom, and dispatch primarily on that
|
|
|
218 2008-05-06.txt:22:24:37: <ais523> and did you quickly hotpatch the interpreter so chanserv played out the turn?
|
|
|
219 2008-05-07.txt:18:45:06: <ehird> so even one panel would be patchwork
|
|
|
220 2008-05-07.txt:18:49:20: <ehird> so you get a patchwork, surrealist comic with a crazy plot
|
|
|
221 2008-05-07.txt:19:24:37: <ais523> say if you wrote an OS kernel in Smalltalk, could you hotpatch it?
|
|
|
222 2008-05-07.txt:19:25:30: <oerjan> Erlang also is good for runtime patching but maybe not as directly (?)
|
|
|
223 2008-05-07.txt:19:25:42: <ehird> say if you wrote an OS kernel in Smalltalk, could you hotpatch it?
|
|
|
224 2008-05-08.txt:15:24:37: <ehird> so we'll have to do some monkeypatching to add a lightbox for blocks
|
|
|
225 2008-05-08.txt:15:36:17: <ehird> Monticello recognizes your monkey patches and even version controls them
|
|
|
226 2008-05-13.txt:20:56:24: <Deewiant> ehird: the patch in question: http://svn.debian.org/viewsvn/pkg-openssl/openssl/trunk/rand/md_rand.c?rev=141&view=diff&r1=141&r2=140&p1=openssl/trunk/rand/md_rand.c&p2=/openssl/trunk/rand/md_rand.c
|
|
|
227 2008-06-04.txt:20:41:11: <ais523> you should be capable of patching around a segfault
|
|
|
228 2008-06-07.txt:18:01:24: <tusho_> I'll probably send a patch off to !WAHa.06x36
|
|
|
229 2008-06-07.txt:18:19:07: <tusho> AnMaster: Oh, and when I said about sending a patch to !WAHa.06x36, that is (perhaps obviously now) a person who is identified solely by their tripcode.
|
|
|
230 2008-06-14.txt:22:46:22: <GregorR> So, did you use my patches to make your cross compiler? I just noticed you said mips-ELF-gcc, but actually some changes are needed to the basic mips-elf-gcc configuration >_>
|
|
|
231 2008-06-14.txt:22:47:22: <tusho> GregorR: SHY DOES IT NEED A PATCH
|
|
|
232 2008-06-14.txt:22:53:40: <tusho> GregorR: What need patching?
|
|
|
233 2008-06-14.txt:22:56:36: <tusho> I just want to know what I have to patch
|
|
|
234 2008-06-14.txt:22:56:43: <tusho> Just the stuff in patches/
|
|
|
235 2008-06-14.txt:22:58:55: <tusho> GregorR: What patch command, again?
|
|
|
236 2008-06-14.txt:22:58:58: <tusho> I can never remember how to use patch
|
|
|
237 2008-06-14.txt:23:00:05: <GregorR> patch -p1 < ...
|
|
|
238 2008-06-15.txt:00:35:21: <tusho> GregorR: Name your patches right, bitch. :P
|
|
|
239 2008-06-15.txt:00:35:37: <GregorR> Well, it'll patch against either, it just doesn't touch anything out of the core.
|
|
|
240 2008-06-18.txt:23:36:31: <GregorR> Oops, forgot to commit the new newlib patch >_>
|
|
|
241 2008-06-19.txt:22:19:08: <jix> downloads of that and patches or something
|
|
|
242 2008-06-19.txt:22:19:38: <jix> ais523: yeah but just offer the bz2s and patches and the vcs you use
|
|
|
243 2008-06-19.txt:22:22:31: <ais523> which is revisions, commits and patches
|
|
|
244 2008-06-19.txt:22:33:31: <ais523> darcs separates patches for showing them
|
|
|
245 2008-06-20.txt:15:57:56: <AnMaster> ais523, it needs some patches
|
|
|
246 2008-06-20.txt:16:02:18: <AnMaster> is one of the patches
|
|
|
247 2008-06-20.txt:16:02:32: <AnMaster> http://rafb.net/p/Mvdg3I17.html is the other patch
|
|
|
248 2008-06-20.txt:16:04:23: <ais523> AnMaster: probably best to keep with your patches until the next release version of C-INTERCAL comes out, with those issues fixed
|
|
|
249 2008-06-20.txt:16:06:42: <AnMaster> ais523, well, it should be fairly trivial to update, remove some patches as they are accepted upstream (like http://rafb.net/p/Mvdg3I17.html the current way is just plain wrong)
|
|
|
250 2008-06-23.txt:14:25:10: <pikhq> It predates such niceties as the linux-tiny patches, uclibc, squashfs-lzma, etc.
|
|
|
251 2008-06-23.txt:16:39:19: <ais523> AnMaster: how often would you say it's a good idea to push patches to a publicly-visible server, when writing code in a distributed versioning system
|
|
|
252 2008-06-23.txt:18:17:28: <ais523> well, Debian were very responsive when I filed patches with them, but it depends on which maintainer you get
|
|
|
253 2008-06-23.txt:19:57:23: <AnMaster> like patches to upstream would be a hell
|
|
|
254 2008-06-23.txt:21:24:47: <ais523> I normally get patches after each new release
|
|
|
255 2008-06-23.txt:21:33:52: <ais523> AnMaster: C-INTERCAL leaks like a sieve anyway, I've tried to patch some of the holes but it's like trying to patch a sieve one hole at a time
|
|
|
256 2008-06-23.txt:22:17:44: <AnMaster> also patches upstream should be minimal, follow existing indention/coding style and *be clean C*
|
|
|
257 2008-06-23.txt:22:18:03: <ais523> ideally it would require no upstream patching at all
|
|
|
258 2008-06-23.txt:22:18:13: <AnMaster> well if you find bugs I would like patches
|
|
|
259 2008-06-24.txt:15:09:38: <Ilari> Except that IIRC, some security enhancement patches to Linux made use of segmentation...
|
|
|
260 2008-06-24.txt:17:42:19: * Sgeo vaguely wonders if his patch could, in some clinically insane way, be screwing with something
|
|
|
261 2008-06-24.txt:17:53:14: <Sgeo> (well, not w/o a patch anyway)
|
|
|
262 2008-06-24.txt:18:00:52: <Sgeo> Well, now that the Warp is known to survive, maybe I can release the patch
|
|
|
263 2008-06-24.txt:20:25:05: <AnMaster> anyway just maintaining a small patch like that is easy
|
|
|
264 2008-06-24.txt:20:25:45: <AnMaster> you will need to update it occasionally if you do it like a patch becase the version number is next to it, and thus patch context will change, or you could sed it at compile time and never need to worry about that again
|
|
|
265 2008-06-25.txt:17:09:03: <ais523> that's why the last few patches to the build system and to created operators are all jumbled up
|
|
|
266 2008-07-01.txt:16:38:49: <pikhq> You know a package's build system is bad when you have to write a patch just to make the build system cross-compile. . .
|
|
|
267 2008-07-03.txt:16:35:02: <ais523> and sent off the patches to Gnome
|
|
|
268 2008-07-03.txt:16:35:24: <AnMaster> and same I sent patches upstream to gentoo
|
|
|
269 2008-07-03.txt:19:07:06: <Deewiant> you might want to look at http://www.dsource.org/projects/gdb-patches
|
|
|
270 2008-07-03.txt:19:12:22: <Deewiant> 2008-07-03 21:07:06 ( Deewiant) you might want to look at http://www.dsource.org/projects/gdb-patches
|
|
|
271 2008-07-03.txt:19:13:18: <AnMaster> oh cost money, well gdb patches it is then
|
|
|
272 2008-07-05.txt:11:32:38: <Deewiant> I'm in the process of patching Tango so that my code compiles ^_^
|
|
|
273 2008-07-07.txt:15:05:07: <ais523> at the moment I have patches + a script that applies them
|
|
|
274 2008-07-07.txt:15:05:27: <ais523> but the patches being GPLv3 makes it kind of tricky to distribute with C-INTERCAL
|
|
|
275 2008-07-07.txt:15:06:29: <ais523> ofc I could just licence the patches under gpl2+ as it would come to the same thing when combined with your gpl3 code, but I'd need your permission to do that
|
|
|
276 2008-07-07.txt:15:07:42: <AnMaster> ais523, got a patch for that? ;)
|
|
|
277 2008-07-07.txt:15:07:53: <ais523> also another patch which it would be helpful for you to apply
|
|
|
278 2008-07-07.txt:15:08:08: <AnMaster> ais523, oh btw your patch is your custom interpreter main loop file + your fingerprint right? in that case, go ahead with GPL2+
|
|
|
279 2008-07-07.txt:15:08:25: <AnMaster> ais523, care to upload the patches somewhere?
|
|
|
280 2008-07-07.txt:15:09:34: <ais523> the patch is etc/cfunge.patch
|
|
|
281 2008-07-07.txt:15:10:48: <AnMaster> ais523, the other patch hm I see yes
|
|
|
282 2008-07-07.txt:15:15:45: <ais523> I'll remove the bit of my code that patches cfunge once the newer version is pushed
|
|
|
283 2008-07-07.txt:16:15:23: <tusho> AnMaster: send patches to tim bray making it better.
|
|
|
284 2008-07-07.txt:16:16:29: <AnMaster> unless you plan to send me a patch
|
|
|
285 2008-07-07.txt:17:57:06: <AnMaster> ais523, pushed the fixed code so that patch no longer is needed
|
|
|
286 2008-07-07.txt:21:58:16: <AnMaster> I may make some patches to fix valgrind issues if I have time
|
|
|
287 2008-07-08.txt:19:02:06: <pikhq> It's a set of patches to the 2.6 kernel which allow one to make 2.6 really, really small. . .
|
|
|
288 2008-07-08.txt:19:02:19: <AnMaster> what do the patches remove then?
|
|
|
289 2008-07-08.txt:19:14:36: <pikhq> The various linux-tiny patches are currently being updated so that they can be stuck into the mainline kernel.
|
|
|
290 2008-07-08.txt:19:16:04: <pikhq> People using these patches have gotten the kernel down to... 197K.
|
|
|
291 2008-07-09.txt:17:26:30: <ais523> such as patch.exe doesn't work unless renamed to something else
|
|
|
292 2008-07-13.txt:22:45:36: <ais523> and found nothing but the gcc source code, and patches to it
|
|
|
293 2008-07-14.txt:22:11:14: <ais523> I patched that earlier this month and sent him the patch
|
|
|
294 2008-07-15.txt:18:08:15: <tusho_> {I seem to remember something about a patch to httpd to allow mapping
|
|
|
295 2008-07-15.txt:21:04:50: <ais523> AnMaster: only vaguely, I haven't looked at it in detail but I patched a mistake in its go-away command
|
|
|
296 2008-07-15.txt:22:07:23: <tusho_> lament: go and hack up a patch to your browser to do that.
|
|
|
297 2008-07-15.txt:22:14:13: <tusho_> ais523: how about you draft a patch up for this and send it off to mozilla.org and watch them all laugh at you...?
|
|
|
298 2008-07-16.txt:14:48:27: <AnMaster> tusho, btw I got an idea, if you want TRDS in cfunge, make a patch
|
|
|
299 2008-07-23.txt:18:05:40: <Deewiant> MikeRiley: there's a bug in your dynamic, unless you applied one of my patches
|
|
|
300 2008-07-23.txt:18:06:00: <MikeRiley> i already applied that patch, thanks!!!
|
|
|
301 [too many lines; stopping]
|
