From: James Ramsay Date: Thu, 12 Mar 2020 04:04:44 GMT Subject: [TOPIC 9/17] Obsolescence markers and evolve Message-ID: <9CE46D29-4BCD-4E95-B2DA-939EA10D7934@jramsay.com.au> In-Reply-To: 1. Brandon: I thought it would be interesting to have a similar feature as Mercurial has. Mercurial evolve will help you do a big rebase commit by commit. Giving you more insights how commits change over time. 2. Peff: This has been discussed a lot of time on the list already. 3. Jonathan N: It will help with Googlers productivity, but it’s smaller compared to other performance fixes. 4. Brian: It’s a great feature and I would like to have it, but I’m not sure it gives enough value to someone to sit down and implement it. 5. Emily: Is it a good candidate for GSoC? 6. Brian: If we have a good design. 7. Stolee: It should be easier to use than interactive rebase. 8. Stolee: It would be nice to have instead of fixup commits I would send to you new commits which mark your original commits are obsolete.