On Tue, Oct 13, 2015 at 12:24 PM, Philip Oakley <philipoak...@iee.org> wrote: > IIUC (as an alternate example), in G4W one can submit a (long) pull request > with internal back references that would be merged directly, so the sha1's > could be updated as Francois-Xavier originally asked. I have a series that's > been bumping along for a long while that needs regular rebasing, though > doesn't have sha1 back references, so I can see that the need does happen. I > can see that others may have a workflow that would work well with the sha1 > auto-update. > > -- > Philip >
I still don't see how this is useful, because the part that *can* be implemented is not valuable and the part that is valuable can't be implemented. So, what we can implement easily enough: you rebase a series and any time the message contains sha1 of a commit we're modifying in this rebase, we update the sha1 to match again. This seems reasonable, but not useful. Why would you reference a commit that is *ITSELF* being rebased. No one has explained a reasonable use for this... I'm sure there exists one, but I would want an explanation of one first. The "useful" case is if you rebase "onto" a tree that has a previous history that has been changed. In this case, how do you propose we find it. Doing as suggested above, ie: only changing sha1s that we are already rebasing works, but why are you backreferencing it if you are re-writing the commit? That doesn't make sense to me at all. Yes, you can do it, but I don't get why this is valuable. If you're backref is "fixes xyz" why not just fix xyz instead of have two commits. If the back ref has some other value... what is that value? I don't understand it I guess. It just seems pretty narrow focus. I mean if someone wants to implement it, that is fine. Regards, Jake -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
