You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue with the code here, per se, but could use some feedback, would be helpful. Briefly, we are building a modified kernel for our embedded system, and I want to capture a diff patch for our local mods.
This would be a simple diff matter, however, I've discovered that our partner has been building and committing build artifacts to source control. I've already chastised them for this bad practice, the diff ends up being many megabytes, where we should only be concerned with perhaps several hundred kilobytes in a patch file. Just bad, bad, bad. Anyway...
Now I want to strip out the build artifacts from the process so that we're only diff patching what's actually been changed, and not the intermediate or final build outcome files.
Files like .o files are obvious, for instance. I am a newbie to the world of building kernels, so need some advice what else to exclude. Plausibly, I could also run a Beyond Compare analysis and do it that way, also with some informed decisions along the way.
Much appreciated.
Regards,
Michael Powell
The text was updated successfully, but these errors were encountered:
Hello,
Not an issue with the code here, per se, but could use some feedback, would be helpful. Briefly, we are building a modified kernel for our embedded system, and I want to capture a diff patch for our local mods.
This would be a simple diff matter, however, I've discovered that our partner has been building and committing build artifacts to source control. I've already chastised them for this bad practice, the diff ends up being many megabytes, where we should only be concerned with perhaps several hundred kilobytes in a patch file. Just bad, bad, bad. Anyway...
Now I want to strip out the build artifacts from the process so that we're only diff patching what's actually been changed, and not the intermediate or final build outcome files.
Files like .o files are obvious, for instance. I am a newbie to the world of building kernels, so need some advice what else to exclude. Plausibly, I could also run a Beyond Compare analysis and do it that way, also with some informed decisions along the way.
Much appreciated.
Regards,
Michael Powell
The text was updated successfully, but these errors were encountered: