On 2017-02-14 15:18, Steven Rostedt wrote: > On Tue, 14 Feb 2017 00:15:33 +0100 > Dominic Sacré <dominic.sacre@xxxxxx> wrote: >> While I was writing my previous mail, 4.1.38-rt45 was released. Attached >> is a diff between rt/4.1/older/sha256sums.asc before (4 days ago) and >> after -rt45 was added. >> Note how the gzip-compressed files for 4.1.35-rt40 and 4.1.38-rt44 >> changed in the meantime. > > I wonder if my process caused this. I use to just have a copy of the > current patches in the main directory, and someone asked me to place a > copy in the older directory, which I started doing. Thanks! To me it's very useful to have a permanent URL for all patches, including the latest one. > Now when I release a newer kernel, I move the previous version from > the main directory into the older directory deleting the copy that > was there. > > Could this be the cause of your issue? I think so. Looking at the current contents of rt/4.1, I see that patch-4.1.38-rt45.patch.gz and older/patch-4.1.38-rt45.patch.gz have different sha256 hashes. I would have expected them to be copies of the exact same file, so I guess the question is why they're different in the first place. Dominic -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
