Hi,
[not contributing right now with ideas, just giving one important
datapoint to me to the discussion]
On Wed, Sep 26, 2018 at 03:15:14PM +0200, Guido Günther wrote:
> Not necessarily. Maybe a graft would do:
>
>
> https://developer.atlassian.com/blog/2015/08/grafting-earlier-history-with-git/
>
> This is IMHO preferable over history rewrites. I've used this to tie
> histories in the past. I've not used "git replace" though but
> .git/info/grafts.
FWIW on this point, for the securiy team members worklfows it is quite
importannt aspect (even admittely can be slow) to have access to
history of commits while working on their own checkouts. So that would
be a feature that in any splitup work done should be considered,
either in a rewrite-history situation or as mentioned above, or other
possibilties which will arise.
Thank you!
Regards,
Salvatore
