LWN: Comments on "LKML archives on lore.kernel.org" https://lwn.net/Articles/758034/ This is a special feed containing comments posted to the individual LWN article titled "LKML archives on lore.kernel.org". en-us Sat, 18 Oct 2025 06:41:14 +0000 Sat, 18 Oct 2025 06:41:14 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net LKML archives on lore.kernel.org https://lwn.net/Articles/759168/ https://lwn.net/Articles/759168/ nix <div class="FormattedComment"> As that page notes, grafts are obsolete now. You want to use 'git replace' instead.<br> </div> Fri, 06 Jul 2018 10:27:22 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758122/ https://lwn.net/Articles/758122/ neilbrown <div class="FormattedComment"> <font class="QuotedText">&gt; See <a href="https://archive.org/details/git-history-of-linux">https://archive.org/details/git-history-of-linux</a> for an example of it applied to the Linux kernel history.</font><br> <p> or closer to home:<br> <p> <a href="https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/">https://git.kernel.org/pub/scm/linux/kernel/git/history/h...</a><br> <p> </div> Sun, 24 Jun 2018 22:20:58 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758085/ https://lwn.net/Articles/758085/ cesarb <div class="FormattedComment"> You can use grafts (<a href="https://git.wiki.kernel.org/index.php/GraftPoint">https://git.wiki.kernel.org/index.php/GraftPoint</a>) to artificially add extra parents to a commit, so the initial commit of one history appears to have the final commit of the other history as a parent. The SHAs of the commits are unchanged. See <a href="https://archive.org/details/git-history-of-linux">https://archive.org/details/git-history-of-linux</a> for an example of it applied to the Linux kernel history.<br> </div> Sun, 24 Jun 2018 14:24:03 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758084/ https://lwn.net/Articles/758084/ epa <div class="FormattedComment"> A pity that git doesn't allow you to splice together two histories keeping the existing SHAs valid. So all commits after the splice point would have two SHAs and could be referred to by either. Then the Git kernel history could be spliced on to the git repository of Bitkeeper-era history. (Allowing multiple SHAs for a single commit might also help migrate away from SHA-1, when that day comes.)<br> </div> Sun, 24 Jun 2018 13:46:57 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758048/ https://lwn.net/Articles/758048/ cesarb <div class="FormattedComment"> Yes, there's already a repository somewhere with every Bitkeeper commit of the Linux kernel history converted into the equivalent git commit. For the pre-Bitkeeper history, AFAIK the best we have is a repository which converts each pre-patch (which normally contains several unrelated changes) into a single git commit.<br> </div> Sat, 23 Jun 2018 11:33:35 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758047/ https://lwn.net/Articles/758047/ grawity By "pre-DVCS" you also mean pre-BitKeeper, I assume? Sat, 23 Jun 2018 09:11:07 +0000 LKML archives on lore.kernel.org https://lwn.net/Articles/758037/ https://lwn.net/Articles/758037/ cesarb <div class="FormattedComment"> This new archive has things I couldn't find anywhere else, like a couple of patches I wrote to the Linux kernel nearly two decades ago (amusingly, the second one can still be found on Linux 4.17, unchanged except for the indentation level).<br> <p> Which leads me to think: this archive could perhaps be used to fill more of the gaps in the pre-DVCS Linux history. It might be possible to crawl this archive to partially reconstruct the set of original patches which were applied to each kernel (pre-)release, and construct a git repository from that so that "git blame" could point to the original author (and most importantly, patch description) of such ancient code.<br> </div> Fri, 22 Jun 2018 21:32:40 +0000