Sitaram, Thanks. I realized that you accidentally used i-j-k-l for p-q-r-s.
You said; "When you merge the release branch into master, it will pick up *all* the commits which exist in release, but do *not* exist in master." This does clarify why r does not wind up in master. Thanks for that. It helps with understanding the underlying git model. When I said that I would commit the change I don't want to propagate by itself, all I meant was that if I know in advance that commit r in the release should not be propagated to the master, it will be easiest for me to merge the release branch into the master before committing the r change, then commit the r change, then merge again and then do a "git revert".without arguments. But your example shows that it can also be done long after the fact. Thanks again, -P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
