Timeline for git squash older commits (not last one)
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17 at 10:45 | answer | added | Frederik Bode | timeline score: 2 | |
| May 23, 2019 at 12:17 | comment | added | jonrsharpe | Not necessarily, a few things go into the commit including a timestamp: stackoverflow.com/a/28917694/3001761. | |
| May 23, 2019 at 12:14 | comment | added | a06e |
@jonrsharpe So commits 1,...,n1 will preserve their hash, even if some of them are included in the interactive rebase but with pick.
|
|
| May 23, 2019 at 7:30 | vote | accept | a06e | ||
| May 23, 2019 at 6:26 | comment | added | jonrsharpe | Yes, because they all have new parent commits now. | |
| May 22, 2019 at 23:04 | comment | added | a06e |
@jonrsharpe Just to confirm, ALL commits fromn2+1 to m will also get new hashes?
|
|
| May 22, 2019 at 19:53 | history | edited | a06e | CC BY-SA 4.0 |
added 6 characters in body
|
| May 22, 2019 at 19:12 | history | edited | phd |
edited tags
|
|
| May 22, 2019 at 18:24 | answer | added | ludovico | timeline score: 62 | |
| May 22, 2019 at 18:12 | comment | added | jonrsharpe | 1. Interactive rebase, see git-scm.com/book/en/v2/Git-Tools-Rewriting-History. 2. Every commit from n1, which is also rewritten, yes. | |
| May 22, 2019 at 18:10 | history | asked | a06e | CC BY-SA 4.0 |