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

Re: [BUG] Highly inconsistent diff UI

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 25, 2013, 05:59 UTC
Message-ID
<7vppxj6thv.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALkWK0ntZKaEzA0Jupj6poOMydqUumEGVVJ-uhBE12sPJ0ntjw@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> Ramkumar Ramachandra wrote:
>> Ofcourse, I now see that this is probably useless, and .. fits my bill.
>
> Would you find it potentially useful?

I dunno. The description you gave was insufficient for me to answer that question.

The part of your message that outlines the scenario you thought A~B might help you was read by me like the following.

    >  pu is based on master~10.  rebase.autostash is based on
    >  master~5 and master~3 merges in pu.
    So which one is 'pu' based on?  master~10, or master~3?  You cannot
    have both.
    >  I merge pu into rebase.autostash while working.  
    So from pu the top two commit on 'master' are missing, but your
    branch was forked way before that from 'master', so these two do not
    concern you.
    >  Now, master..rebase.autostash will exclude commits reachable
    >  from master (and therefore pu),
    Whoa. Earlier you said 'pu' is based on master~10, but changed your
    mind to say master~3 is in 'pu', and now you mean the tip of
    'master' is also in 'pu'?  What is going on?

Can you draw a picture to illustrate the topology you are trying to describe, like I did in a few message upthread? E.g.

        ---o---*---a---a---a---a---A (master)
                \       \
                 b---Y---X---B (topic)
                    / 

shows a topic B that forked from master and merged from irrelevant branch at Y and merged from master at X [*1*].

In the above sample topology, even if you pulled irrelevant (for the purpose of completing your topic) commits at X from 'master', neither "log A..B" or "log $(merge-base A B)..B" (aka "log A~B") would exclude any of your commit that is not yet in the 'master', so I do not think there is anything you gain by using A~B over A..B.

If you pulled something unrelated to your topic that is not in 'master', both "log A..B" and "log A~B" would show these unrelated changes, so again I do not see how A~B would help you over A..B, either.

Perhaps in a particular topology you have in mind, it might make a difference, but I cannot read what that topology is from your description.

[Footnote]
*1* I do not think this particular topology is what you have in
    mind. It is meant to demonstrate one way to illustrate the
    history to help other people understand the example you are
    trying to give.
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 32 of 45 in “[BUG] Highly inconsistent diff UI”
  1. Ramkumar RamachandraApr 24, 2013
  2. Jonathan NiederApr 24, 2013
  3. Junio C HamanoApr 24, 2013
  4. Ramkumar RamachandraApr 24, 2013
  5. Jonathan NiederApr 24, 2013
  6. Junio C HamanoApr 24, 2013
  7. Ramkumar RamachandraApr 24, 2013
  8. Junio C HamanoApr 24, 2013
  9. Ramkumar RamachandraApr 24, 2013
  10. Junio C HamanoApr 24, 2013
  11. Ramkumar RamachandraApr 24, 2013
  12. Ramkumar RamachandraApr 24, 2013
  13. Junio C HamanoApr 24, 2013
  14. Ramkumar RamachandraApr 24, 2013
  15. Junio C HamanoApr 24, 2013
  16. Ramkumar RamachandraApr 24, 2013
  17. Thomas RastApr 24, 2013
  18. Ramkumar RamachandraApr 24, 2013
  19. Jonathan NiederApr 24, 2013
  20. Ramkumar RamachandraApr 24, 2013
  21. Thomas RastApr 25, 2013
  22. Ramkumar RamachandraApr 25, 2013
  23. Junio C HamanoApr 25, 2013
  24. Ramkumar RamachandraApr 25, 2013
  25. Jonathan NiederApr 25, 2013
  26. Junio C HamanoApr 25, 2013
  27. Duy NguyenApr 26, 2013
  28. Phil HordApr 24, 2013
  29. Junio C HamanoApr 24, 2013
  30. Ramkumar RamachandraApr 24, 2013
  31. Ramkumar RamachandraApr 24, 2013
  32. Junio C HamanoApr 25, 2013
  33. Ramkumar RamachandraApr 25, 2013
  34. Ramkumar RamachandraApr 25, 2013
  35. Ramkumar RamachandraApr 26, 2013
  36. Ramkumar RamachandraApr 26, 2013
  37. Junio C HamanoApr 29, 2013
  38. Ramkumar RamachandraApr 29, 2013
  39. Junio C HamanoApr 29, 2013
  40. Ramkumar RamachandraApr 29, 2013
  41. Ramkumar RamachandraApr 29, 2013
  42. Junio C HamanoApr 29, 2013
  43. Ramkumar RamachandraApr 29, 2013
  44. John KeepingApr 29, 2013
  45. Ramkumar RamachandraApr 25, 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.