[TOPIC 9/17] Obsolescence markers and evolve

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

 



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.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux