I have not much experience with using diffs in particular ways, other than relatively close the the latest modifications I've done on my projects.
(I'd love to be a git guru tho, heh, but I'm very far from that) -- Félix On Monday, November 30, 2020 at 9:12:42 AM UTC-5 [email protected] wrote: > I suggest searching for Raymond Chen's posts on git tricks in his blog > "The Old New Things". This search might be a starting point: *"the old > new thing" commit tricks*. Examples: > > https://devblogs.microsoft.com/oldnewthing/20190514-00/?p=102493 > https://devblogs.microsoft.com/oldnewthing/20190515-00/?p=102495 > https://devblogs.microsoft.com/oldnewthing/20180312-00/?p=98215 > > He shows ways to merge/update branches while preserving blame and diff > histories. I'm not sure just what search term would find all of them, and > he has run several series over the years, but it's worth looking. > > On Monday, November 30, 2020 at 7:57:49 AM UTC-5 Edward K. Ream wrote: > >> On Sun, Nov 29, 2020 at 2:50 PM Félix <[email protected]> wrote: >> >>> Glad this workflow stuck ! its a lot simpler and easier that way! :) >>> >> >> I have a question for you concerning big diffs in PR's. >> >> My idea is to periodically long-term branches like ekr-unit-test into >> devel, so as to reduce *later* diffs (in the PR) to the most recent >> work. But I'm concerned that the previous diffs will then be gone forever. >> >> Does this make sense to you? Do you have any suggestions? >> >> Edward >> > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1305ed4f-244e-45a7-bacf-df12166b9d41n%40googlegroups.com.
