Timeline for Git merge commits
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2011 at 18:27 | comment | added | Noufal Ibrahim |
Yes. But you don't have to send them a single commit to review. You can send them a range of commits git diff start end and ask them to review the entire thing. No?
|
|
| Feb 10, 2011 at 10:58 | comment | added | DiogoNeves | You're probably both right, as mathepic said, needs to be scenario-specific. In my case I'm sending it for others to review and the 'back-up' commits don't make much sense in there :) Thanks | |
| Feb 9, 2011 at 5:34 | comment | added | Noufal Ibrahim |
That is true but I don't like squashing the entire week/month of development into a single commit just for the purpose of review. I'm a heavy user of --amend myself.
|
|
| Feb 8, 2011 at 22:41 | comment | added | alternative | Its more of a scenario-specific thing; usually you will want to rebase and make commits more logical and get rid of "oops!" commits before sending in patches. | |
| Feb 8, 2011 at 19:00 | history | answered | Noufal Ibrahim | CC BY-SA 2.5 |