git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What I want rebase to do

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 7, 2013, 17:38 UTC
Message-ID
<7vwqtjm7oj.fsf@alter.siamese.dyndns.org>
In-Reply-To
<87r4jra942.fsf@pctrast.inf.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
> I still think that the _right_ solution is first redoing the merge on
> its original parents and then seeing how the actual merge differs from
> that.
I think that is what was suggested in
    http://article.gmane.org/gmane.comp.version-control.git/198316
> Perhaps a new option to git-rebase could trigger the above behavior for
> merges, who knows.  (It could be called --first-parent.)

Yeah, I think that is what the old thread concluded to be the way to move forward:

    http://thread.gmane.org/gmane.comp.version-control.git/198125
I'll throw it in to the "leftover bits".
    http://git-blame.blogspot.com/2013/02/more-leftover-bits.html
Previous: Johannes SixtNext: Dale R. Worley
Message 8 of 13 in “"git rebase" loses the additional changes in "evil" merges”
  1. Dale R. WorleyMar 4, 2013
  2. Junio C HamanoMar 4, 2013
  3. Thomas RastMar 4, 2013
  4. Junio C HamanoMar 4, 2013
  5. What I want rebase to doDale R. Worley, Mar 6, 2013
  6. Thomas RastMar 7, 2013
  7. Johannes SixtMar 7, 2013
  8. Junio C HamanoMar 7, 2013
  9. Dale R. WorleyMar 7, 2013
  10. Dale WorleyMar 5, 2013
  11. Junio C HamanoMar 5, 2013
  12. Philip OakleyMar 5, 2013
  13. Junio C HamanoMar 5, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.