home | log | search | bash | stats | wiki


Matches for patch, 1691 total results Sorted by newest | relevance

Sat Sep 05 20:49:30 UTC 2015  <mod6>   Well, one thing I don't want is a persistant store of the parents and children of a given patch. I want it to read it fresh everytime so ensure things aren't diddled or cosmic-ray'd or just stale or something. Not sure if that's what was changed on punkmans side. But I want the one that I use to do all of this in one shot.

Sat Sep 05 18:10:24 UTC 2015  <punkman>   it's not a patch, it's now called vit

Sat Sep 05 02:06:18 UTC 2015  <ben_vulpes>   craft a patch

Fri Sep 04 23:09:48 UTC 2015  <mircea_popescu>   the "with clearsigned body and .sig signature" version is exact replica of the single email i successfully sent to date, back in the days of the V patch.

Fri Sep 04 17:57:23 UTC 2015  <ascii_field>   'Cavium has issued a patch and noti-

Fri Sep 04 17:53:59 UTC 2015  <ascii_field>   ideally, each 'bubble' would be clickable and contain links to download patch and all signatures

Tue Sep 01 19:33:34 UTC 2015  <ascii_field>   it was plainly not enough to reconstruct patch flow, yes

Tue Sep 01 19:29:13 UTC 2015  <mike_c>   No, just every patch. I'll fiddle with it and see if anything interesting happens.

Tue Sep 01 19:26:44 UTC 2015  <mike_c>   Surely. But integrating V could allow for "this patch solved this problem"

Tue Sep 01 19:22:42 UTC 2015  <assbot>   Logged on 05-08-2015 14:26:47; asciilifeform: mircea_popescu: i once thought about placing antecedent hashes in patch headers

Tue Sep 01 19:04:52 UTC 2015  <trinque>   mircea_popescu: maybe not; thought was you patch in new textfiles into some directory structure

Tue Sep 01 04:33:36 UTC 2015  <mod6>   <+asciilifeform> rather than roasting in the hell of figuring my patch topology out with a pencil << imagine how much easier it is now for a person to literally pick a place in the flow and patch directly to it. instead of wading through mutliated corpses trying to find the least smelly ones.

Tue Sep 01 04:29:36 UTC 2015  <asciilifeform>   rather than roasting in the hell of figuring my patch topology out with a pencil

Tue Sep 01 04:21:39 UTC 2015  <asciilifeform>   some corresponding to a released patch set, others not

Tue Sep 01 04:14:26 UTC 2015  <asciilifeform>   descendant - later patch, which requires this patch.

Tue Sep 01 04:14:15 UTC 2015  <asciilifeform>   time for a brief likbez, perhaps. antecedent - earlier patch that must have happened to satisfy a given patch

Tue Sep 01 04:11:18 UTC 2015  <asciilifeform>   roughly, the way it works - must work - is that no patch is applied for which the dependencies have not already been applies.

Tue Sep 01 04:05:08 UTC 2015  <mod6>   asciilifeform: qq, I was under the impression that when using press, if I picked something like 'maxint_corrected', it would patch all the way up through that one. but it didn't seem to apply the -verifyall patch? or do I misunderstand how its supposed to work? http://dpaste.com/1J2BS40.txt thoughts?

Mon Aug 31 18:56:29 UTC 2015  <ascii_field>   anyway thing is made in such a way that operator is forced to remain aware of what patch set he is pressing

Mon Aug 31 18:55:15 UTC 2015  <assbot>   Logged on 31-08-2015 14:36:31; asciilifeform: also there is no selectability of wot or patch subsets, other than by specifying --wot customdir or same for patches, containing desired subset

« Previous Page    Next Page »