Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stripping build artifacts for diff patch purposes #5

Open
mwpowellhtx opened this issue Mar 25, 2013 · 0 comments
Open

Stripping build artifacts for diff patch purposes #5

mwpowellhtx opened this issue Mar 25, 2013 · 0 comments

Comments

@mwpowellhtx
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant