summaryrefslogtreecommitdiff
path: root/NOTES.git-debrebase
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2018-02-10 17:40:41 +0000
committerIan Jackson <ijackson@chiark.greenend.org.uk>2018-06-16 12:25:49 +0100
commit6f9e94728e55a5d52120760e6451e9ba48648051 (patch)
treeb94a01fe868447ea2bf6d66036b754bde5159994 /NOTES.git-debrebase
parente30ef7e22058744d48aa1bfa507d7bac17e3ba89 (diff)
git-debrebase: decide: make few pseudomerges, and preserve them
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Diffstat (limited to 'NOTES.git-debrebase')
-rw-r--r--NOTES.git-debrebase17
1 files changed, 14 insertions, 3 deletions
diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase
index 0310f96..6a731f1 100644
--- a/NOTES.git-debrebase
+++ b/NOTES.git-debrebase
@@ -176,6 +176,17 @@ so that the overall result will be series of pseudomerges.
So, pm handling specifics:
+strategy is to avoid making needless pseudomerges
+pseudomerges that exist will be preserved
+(by being included in will-overwrite)
+
+This is good because the presence of a pseudomerge means we know we
+want to keep it; and that allows explicit control over history detail
+level.
+
+It does mean we must avoid making the pseudomerges unnecessarily.
+They should be made just before (ideally, part of) dgit push.
+
1. git-debrebase [-i etc.]
should:
@@ -192,10 +203,10 @@ So, pm handling specifics:
set will-overwrite to something which is ff from
all above branches
- either 1. one of them or, if there is no maximal one,
- 2. our tip
- ? optionally, according to config always take tip anyway
+ we use our tip, as discussed above
+ (optionally, can use some other commit which is ff
+ from all of the above, eg one of them)
2. git-debrebase stitch