Matches for patch, 1691 total results Sorted by newest | relevance
Fri Jan 29 17:04:27 UTC 2016 <ascii_butugychag> so, e.g., mircea_popescu's retabbing, would be a five-line patch
Fri Jan 29 17:03:24 UTC 2016 <mod6> as far as comments in the vpatch that are mearly just for archaeological or annotative purposes, i think something could be done here especially when we get our own diff/patch.
Fri Jan 29 17:02:08 UTC 2016 <ascii_butugychag> shave half of face, submit patch, shave other half, etc
Fri Jan 29 16:59:08 UTC 2016 <mircea_popescu> now, one obvious solution (wasn't obvious to me at the time what it was a solution to) is to INCLUDE COMMENTS in the patches, like i did with my only signed patch i didn't really intended as part of a final pressing
Fri Jan 29 16:53:21 UTC 2016 <mircea_popescu> approach thematter from the other, practical side, maybe it's easier that way. so i made a patch that did X, then i made a patch that did X'. i consider X' to be > X.
Fri Jan 29 16:52:43 UTC 2016 <ascii_butugychag> but i will note that introducing a new patch that is binary-identical to an old one, is an error.
Fri Jan 29 16:50:15 UTC 2016 <ascii_butugychag> so if i submit frobs-x.vpatch and also-frobs-x.vpatch and they both reference patch frobbed-x-before.vpatch, then i can press to frob-x OR to also-frobs-x or to any other leaf.
Fri Jan 29 16:45:36 UTC 2016 <assbot> Logged on 29-01-2016 10:29:19; jurov: I know that i should manage the repository myself, but imo a version field would be good to have so that I can easily spot if someone posts revised version of the same patch.
Fri Jan 29 16:43:57 UTC 2016 <ascii_butugychag> mircea_popescu: i closed the gap today, see the next patch.
Fri Jan 29 16:42:36 UTC 2016 <assbot> Logged on 29-01-2016 10:02:07; punkman: so shiva patch wholly includes the tinyscheme genesis instead of referencing it?
Fri Jan 29 16:23:57 UTC 2016 <*> ascii_butugychag read the mega-patch-of-all-ages yet ?
Fri Jan 29 16:07:39 UTC 2016 <assbot> Logged on 29-01-2016 07:42:24; polarbeard: I've timestamped and categorized trb log lines, as well as improved the messages and removed (seeming never activated) destructive log rotation, here is the signed patch: https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants to review it so I can submit it to the ml
Fri Jan 29 15:39:54 UTC 2016 <ascii_butugychag> (as my instructions note, it is necessary to rename a directory after pressing tinyscheme-genesis to end up with the shiva subdir in shiva patch)
Fri Jan 29 13:25:44 UTC 2016 <assbot> Logged on 29-01-2016 10:02:07; punkman: so shiva patch wholly includes the tinyscheme genesis instead of referencing it?
Fri Jan 29 13:25:23 UTC 2016 <asciilifeform> ;;later tell polarbeard when writing a patch, consider the effort required to properly grasp EVERY LINE
Fri Jan 29 13:24:50 UTC 2016 <assbot> Logged on 29-01-2016 08:08:31; ben_vulpes: "this 2.6kloc patch rewrites every log line in the reference implementation, in support of further work i'm doing on" etc etc
Fri Jan 29 13:21:46 UTC 2016 <assbot> Logged on 29-01-2016 07:42:24; polarbeard: I've timestamped and categorized trb log lines, as well as improved the messages and removed (seeming never activated) destructive log rotation, here is the signed patch: https://gist.github.com/polarbeard/961aa315c69b89d2e613 in case somebody with a decent reputation wants to review it so I can submit it to the ml
Fri Jan 29 11:23:17 UTC 2016 <punkman> I think it'd be best to name the 2nd patch mempool_frobsv2.vpatch or something like that
Fri Jan 29 11:19:23 UTC 2016 <jurov> and the version field as just advisory indication which is the more recent patch
Fri Jan 29 11:00:39 UTC 2016 <polarbeard> ftr, I've updated the gist, will send the patch to the ml later