simple (and probably trivial) git question about cumulative patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  what is the recipe (and i'm sure there is one) for starting with a
stock kernel tree and making a record of a set of potentially
cumulative patches?  as in, starting with stock tree:

1) make some changes
2) "git diff" to record that particular change
???
3) make some *further* changes
4) record the differential patch between the last one and this one
5) ... repeat as long as i want ...

i'm guessing that, between steps 2) and 3), i would have to, what,
"commit" the current patch so that it doesn't show up in the next "git
diff".  and, finally, i want to reset my cloned repo all the way back
to its initial state, with no changes.  "revert", i'm guessing.

rday

p.s.  i don't know much about the "quilt" utility but i've been told
that might be what i'm looking for as well.  thanks for any guidance.

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux