Matches for patch, 1691 total results Sorted by newest | relevance
Sun Apr 24 01:31:33 UTC 2016 <kakobrekla> patch
Wed Apr 06 06:23:27 UTC 2016 <assbot> Logged on 05-04-2016 21:25:16; *: adlai still maintains that V would at least benefit from studying darcs, if not outright stealing their "patch theory" model
Tue Apr 05 21:25:36 UTC 2016 <asciilifeform> in particular re the patch theory
Tue Apr 05 21:25:16 UTC 2016 <*> adlai still maintains that V would at least benefit from studying darcs, if not outright stealing their "patch theory" model
Sat Apr 02 19:09:20 UTC 2016 <funkenstein_> danielpbaron, have you considered publishing a signed V genesis patch of whatever text you consider to be important?
Fri Apr 01 00:13:10 UTC 2016 <kakobrekla> doesnt the email patch submitting thing eat stuff from asswot or do i misremember
Mon Mar 28 17:42:42 UTC 2016 <asciilifeform> PeterL: pretty much all the patch-contributin' folk are in #trilema, i will be trb-ing there
Tue Mar 22 21:10:28 UTC 2016 <asciilifeform> understand, a 10kB patch is ~LONG~
Tue Mar 22 21:06:30 UTC 2016 <ben_vulpes> i press to confirm patch validity and then commit the changes to my local version controlatron.
Tue Mar 22 21:05:24 UTC 2016 <phf> mechanism has nothing to do with "mercurial" as such, and is more akin to old school patch management system, "quilt"
Tue Mar 22 21:04:18 UTC 2016 <phf> mercurial has a handy patch management mechanism, that unfortunatly doesn't understand nor produces vpatches. i basically verify vpatches manually, and then put them into hg's patch folder. then i do a topo sort, which gives me a mercurial compatible "series" file. i let mercurial press it using that series file. whole process is more complicated then should be with a proper mercurial support, but i hnfi how people rebase, refresh,
Tue Mar 22 20:25:49 UTC 2016 <mrottenkolber> I am only mentioning the sha1 option because I don't understand crypto well enough to be able to rationalize the effort of producing a file, with the same sha1sum, with an exploit while the patch still applies.
Tue Mar 22 20:24:43 UTC 2016 <phf> mrottenkolber: a better place to wire v would be mercurial's mq facility. mercurial has a way of managing plaintext patchsets, to do things like patch refresh, i.e update the contents of patch from the current tree state, mercurial managed patch press, i.e. instead of doing "manual" v press hg will keep track of state for you, etc. this will not be a way to share patches, as much as a way to facilitate vpatch authoring.
Tue Mar 22 20:08:18 UTC 2016 <mrottenkolber> My point is the toposort isn't really part of the problem v solves. The function is to cryptographically verfiy a sequence of patches (based on a wot), who cares where that sequence comes from, as long as each patch (commit) has a signature.
Mon Mar 21 17:43:04 UTC 2016 <mod6> <+asciilifeform> this patch has 'all signers: mircea_popescu trinque asciilifeform mod6' << i'll note that this signatures you're referencing are strictly for genesis.vpatch
Mon Mar 21 17:36:57 UTC 2016 <asciilifeform> and this is a patch without which trb is ~dead in the water~
Mon Mar 21 17:36:33 UTC 2016 <asciilifeform> this patch has 'all signers: mircea_popescu trinque asciilifeform mod6'
Sun Mar 20 22:55:16 UTC 2016 <thestringpuller> i really should patch this to rotate logs...
Sun Mar 20 15:14:29 UTC 2016 <assbot> Logged on 20-03-2016 15:04:05; phf: also anyone tried doing a kernel level key rebind before? is that just in config or you need to patch source. i want to switch some keys around, but i don't want to have to do it for every single userland environment
Sun Mar 20 15:04:05 UTC 2016 <phf> also anyone tried doing a kernel level key rebind before? is that just in config or you need to patch source. i want to switch some keys around, but i don't want to have to do it for every single userland environment