Michael,
I don't believe so, but it is probably worth re-raising on the Git mailing
list. (Michael Haggerty is currently active as well)
I say that because @dscho is currently doing a better rebase that can handle
merges and amend the flow logic within such merged series that are being
rebased.
https://public-inbox.org/git/cover.1524659287.git.johannes.schinde...@gmx.de/
He is doing this especially to supprt Git for Windows which also need the
'historical' segments retained after every rebased of the GfW fixes that go
on top of the upstream git. Having a method of marking such older parts as
'uninteresting' would be great because these patches repeat themselves over
and over again as on passes the 2nd parent point of the old relase would be
great.
Now to read that old post in detail....
Philip
----- Original Message -----
From: "Michael" <keybou...@gmail.com>
To: <git-users@googlegroups.com>
Sent: Friday, May 25, 2018 8:22 PM
Subject: [git-users] Marking a commit parent as not displayed by default
A few years ago (2009), the idea was put forward that some parents in a
merge should be marked as "historical", or "uninteresting", and not
displayed by default
(http://softwareswirl.blogspot.com/2009/08/rebase-with-history-implementation.html)
Does git currently have any support for this?
---
Entertaining minecraft videos
http://YouTube.com/keybounce
--
You received this message because you are subscribed to the Google Groups
"Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
