Comments on: V Study Part 1 - Vpatches and Vdiff http://ztkfg.com/2019/10/v-study-part-1-vpatches-and-vdiff/ 198.211.113.164 // 6326 273B 61A7 00AF 4CD9 5A7B 8C6C AB19 24A6 4DEC Sun, 26 Apr 2026 18:52:17 +0000 http://polimedia.us hourly 1 By: Diana Coman http://ztkfg.com/2019/10/v-study-part-1-vpatches-and-vdiff/#comment-47 Diana Coman Thu, 17 Oct 2019 12:29:52 +0000 http://ztkfg.com/?p=347#comment-47 1. "Would it ever make sense to create a vpatch for heathen code without first creating a genesis?" - Not really (other than as exercise) but that's *not* at all what I was saying there, no. The genesis vpatch is the root of a V-tree. The name is not chosen randomly: it's a *tree* and that means that there are no cycles in it but also that each node can have 0 or *more* children. Now read my 1st sentence again and especially the part "there is no requirement (and in some cases no reason either) for a V-tree to be just a V-line." A V-line means strictly one child from each node, from genesis down, no ramifications. This flat V-line structure is what you get if you restrict pressing to "the most recent" aka "head" in v-parlance. There is no such requirement: you can press a new vpatch on top of *any* existing vpatch, anywhere in the tree (and that's how you get ramifications). 2. There is a time-tested way and no need for you to reinvent it. It just goes like this: write first *without* any agonizing over it, it's just a DRAFT. Then you re-read that and correct obvious mistakes, misspellings etc. After *some time* (preferably at least 1 hour), you re-read again and correct further, esp for clarity and structure if needed. Only after this (and as a minimum really), you publish. 3. See at 2 above; that 2nd review should have rearranged parts and improved matters. 1. "Would it ever make sense to create a vpatch for heathen code without first creating a genesis?" - Not really (other than as exercise) but that's *not* at all what I was saying there, no.

The genesis vpatch is the root of a V-tree. The name is not chosen randomly: it's a *tree* and that means that there are no cycles in it but also that each node can have 0 or *more* children. Now read my 1st sentence again and especially the part "there is no requirement (and in some cases no reason either) for a V-tree to be just a V-line." A V-line means strictly one child from each node, from genesis down, no ramifications. This flat V-line structure is what you get if you restrict pressing to "the most recent" aka "head" in v-parlance. There is no such requirement: you can press a new vpatch on top of *any* existing vpatch, anywhere in the tree (and that's how you get ramifications).

2. There is a time-tested way and no need for you to reinvent it. It just goes like this: write first *without* any agonizing over it, it's just a DRAFT. Then you re-read that and correct obvious mistakes, misspellings etc. After *some time* (preferably at least 1 hour), you re-read again and correct further, esp for clarity and structure if needed. Only after this (and as a minimum really), you publish.

3. See at 2 above; that 2nd review should have rearranged parts and improved matters.

]]> By: whaack http://ztkfg.com/2019/10/v-study-part-1-vpatches-and-vdiff/#comment-46 whaack Wed, 16 Oct 2019 16:17:29 +0000 http://ztkfg.com/?p=347#comment-46 1) I acknowledge I did not note the case for the genesis patch. And, as you say, vdiff does not require that the source comes from a vline. However it is not clear to me why one would create a patch (other than a genesis patch) where the previous source was not the result of a previous press. Would it ever make sense to create a vpatch for heathen code without first creating a genesis? To me the answer is a clear no. 2) (on proofreading) Yes I apologize for wasting your time with my sloppy previous post. For my my interests post i spent hours agonizing (or "spinning") over wording, and I realized I cannot operate that way if I want to get anything done. But I went too much in the other direction with this post and in haste published something incomprehensible. I am still looking for balance on how much time I spend revising while I build my blogging muscles. 3) The goal of the post was to demonstrate my understanding of the creation of vpatches "In this post I go over how the vpatches used in this process are created." I should have changed that sentence to s/"go over"/"go over my current understanding of" I also should have made the intent of the post clear in the title. Lastly, the post is a little over the place in part because I felt the need to include some context about V to discuss the creation of vpatches. 1) I acknowledge I did not note the case for the genesis patch. And, as you say, vdiff does not require that the source comes from a vline. However it is not clear to me why one would create a patch (other than a genesis patch) where the previous source was not the result of a previous press. Would it ever make sense to create a vpatch for heathen code without first creating a genesis? To me the answer is a clear no.

2) (on proofreading) Yes I apologize for wasting your time with my sloppy previous post. For my my interests post i spent hours agonizing (or "spinning") over wording, and I realized I cannot operate that way if I want to get anything done. But I went too much in the other direction with this post and in haste published something incomprehensible. I am still looking for balance on how much time I spend revising while I build my blogging muscles.

3) The goal of the post was to demonstrate my understanding of the creation of vpatches "In this post I go over how the vpatches used in this process are created." I should have changed that sentence to s/"go over"/"go over my current understanding of" I also should have made the intent of the post clear in the title. Lastly, the post is a little over the place in part because I felt the need to include some context about V to discuss the creation of vpatches.

]]> By: Diana Coman http://ztkfg.com/2019/10/v-study-part-1-vpatches-and-vdiff/#comment-45 Diana Coman Wed, 16 Oct 2019 12:06:28 +0000 http://ztkfg.com/?p=347#comment-45 "To make a vpatch, a developer starts with a copy of the source already pressed to the previous most recent vpatch." - this is not strictly true, no, there is no requirement (and in some cases no reason either) for a V-tree to be just a V-line. To make a vpatch, all you need to start with is either an empty directory (when you create the genesis vpatch - that's a vpatch too!) or the result of a previous press. Other than that, the text clearly benefited from proofreading but it's ending quite abruptly and unexpectedly - what were you trying exactly to say with this? The title seems to promise a discussion of vpatches at the very least, but the above fails rather short of it and sounds more like "here's my first attempt to play around with vdiff and vpatches". If this is what it is, it's fine but don't confuse it for "I know what vpatches are" and moreover, do structure your investigations better after the initial play around. "To make a vpatch, a developer starts with a copy of the source already pressed to the previous most recent vpatch." - this is not strictly true, no, there is no requirement (and in some cases no reason either) for a V-tree to be just a V-line. To make a vpatch, all you need to start with is either an empty directory (when you create the genesis vpatch - that's a vpatch too!) or the result of a previous press.

Other than that, the text clearly benefited from proofreading but it's ending quite abruptly and unexpectedly - what were you trying exactly to say with this? The title seems to promise a discussion of vpatches at the very least, but the above fails rather short of it and sounds more like "here's my first attempt to play around with vdiff and vpatches". If this is what it is, it's fine but don't confuse it for "I know what vpatches are" and moreover, do structure your investigations better after the initial play around.

]]>