-
Notifications
You must be signed in to change notification settings - Fork 35
One big issue is that I am back ;) #2
Comments
Hey @naixia, I am very glad that you wrote to me, it means that might work is actually popular. I will get through the changes. Maybe you want to take this repository and update code here. I am proposing to merge our forces. What do you think? |
I really appreciate you and post-factum for your work on spreading UKSM. |
Hi, Wouldn't it be better to fork https://github.com/torvalds/linux and keep uksm synced here? This will make live really easier for those who uses git :D |
@naixia: I gave you the access. Github show the number of visits and clones of repo, but only from the last two weeks.
Imagine that someone is using many patches, then he need to extract the patch from every tree like that and then apply. In my opinion it is better as it is right now. |
It can be made much easier, using github and not exploiting what git offers is kind of an oxymoron :D |
@dolohow @xming I think both of you have your points. So I think maybe I should create my own repo and sync my git tree with it and let the individual patches created in repo's "releases" section. How do you think? |
Oh,BTW, I actually prefer to point the download link to my kerneldedup.org site for download time counting :D |
@naixia I don't know why you are so obsessed with the d/l counts, many users use kernels from arch, pf, etc. so you can't get an accurate user base count anyway. |
@naixia I don't know why you are so obsessed with the d/l counts, many users use kernels from arch, pf, etc. so you can't get an accurate user base count anyway. EDIT: Oh you can always host the d/l links on kerneldedup and redirect them to the github commits, so you can count the d/l on your server. |
@xming Oh, you remind me why I was unwilling to push git repo. Since I am constantly rebasing against stable kernel trees for my own connivence. Pushing a rebased tree to github repo is an annoying action to others synced to this repo. Besides, most people really care about is the patches. Pulling the whole vanilla kernel tree is tedious. So before anyone outside my own team can really contribute code to UKSM, giving out git tree is not that straight forward. So, ok, I will sync this repo with patches. |
@naixia I am working in Nanjing, where your university is. (I read your LinkedIn profile, haha.) |
Rebasing is pretty common for out-of-tree kernels, so users know that they have to force update. If you don't have enough users using git repo to justify the troubles then for get what I've suggested. @naixia do you mind if I do that and publish the repo on github? cheers |
@zhangyewei-edwin Pushing a very complex patch set like UKSM to vanilla kernel takes very much time and energy, which I cannot afford for the time being. Maybe it will be easier after I get the my paper published. @xming 1). I guess so. 2). Of course not, do whatever you like, that's what GPL grants you. :) |
Works pretty good so far, I noticed that it finds a lot more memory than it used to. Thank you! |
|
Resync for 4.8 is ready. Check out! |
@dolohow Good job! I'll look into this and maybe change a little. |
@naixia thank you for the changes. I will close this issue for now, if someone got something new please create a new. Thanks |
I'am very glad that someone still supports UKSM while I was away. Thanks a lot 馃憤 !
I just released the new patches for new kernels with some bug fixes.
You may want to checkout and see if they work on your machines.
The text was updated successfully, but these errors were encountered: