I have only started using git (after several years using svn), so I have some basic There is a lack of elements.
I am working on a project using Raspberry P as it happens, I use one of the tools I find in a kernel, a faulty driver, so I I'm trying to debug.
I started with the official RPI kernel, from This kernel is not completely up to date, although it is not far behind I need to use this kernel because as per the documentation it contains some drivers for Raspberry PI etc.
However since I'm trying to decide something, I think that the most up to date kernel is possible, the driver I'm looking at is a repo.
Therefore, what I want to do is apply to all the commitments that have been done in the Wireless Testing repo but which are not yet in the RPI repo.
If possible, it would be ideal if I commit that which I can draw from a wireless test, only to affect a particular directory tree, because I suspect that these possibilities may be less
Finally, I ideally want to be able to keep track of the RPI repo, so that changes can come from there.
What is a good workflow?
You can add them both as Remotes
if they are the same In the branch, you will need to merge / rebase and resolve any merging of the solution.
If you need to combine the information in the two branches, then go to the two bridges you want (with Raspberry Pie Driver Goods) and merge GIT or GIT Rebase (difference is a long conversation Is a subject for) and solve any merger as necessary struggle.
See also:
and
Comments
Post a Comment