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

Re: questions / suggestions about history simplification

From
Adam Spiers <git@adamspiers.org>
Date
Dec 19, 2013, 21:04 UTC
Message-ID
<20131219210448.GK23496@pacific.linksys.moosehall>
In-Reply-To
<20131219190333.GE23496@pacific.linksys.moosehall>
On Thu, Dec 19, 2013 at 07:03:33PM +0000, Adam Spiers wrote:
Show 7 quoted lines
> I still don't understand a few things about history simplification:
> 
> 1. The "--full-history without parent rewriting" correctly asserts
>    that commit Q will be shown.  But AFAICS this contradicts the
>    documented behaviour "Commits are included if they are not TREESAME
>    to any parent" which is implied by "This mode differs from the
>    default in one point:", because Q is TREESAME to P.

I'm *guessing* that this apparent exception to the stated rules could be because Q is the start of the walk. Or maybe I'm just missing a key detail. I'd love to hear confirmation either way.

[Questions 2 and 3 snipped]
4. --dense (the default behaviour) includes walked commits iff they are not
   TREESAME to any parent.  --sparse includes all walked commits.  But
   how do I get the middle ground, i.e. all walked commits which are
   not TREESAME to at least one parent?

This seems like an obvious use case, but I haven't figured out how to do it yet :-/

Thanks! (I probably don't say that often enough, but the sentiment is always there ;-)

Previous: Junio C Hamano
Message 14 of 14 in “script for reproducing history example in git-log(1) man page”
  1. Adam SpiersDec 19, 2013
  2. questions / suggestions about history simplificationAdam Spiers, Dec 19, 2013
  3. Jonathan NiederDec 19, 2013
  4. Adam SpiersDec 19, 2013
  5. Junio C HamanoDec 19, 2013
  6. Adam SpiersDec 19, 2013
  7. Junio C HamanoDec 19, 2013
  8. Adam SpiersDec 19, 2013
  9. Junio C HamanoDec 19, 2013
  10. Adam SpiersDec 19, 2013
  11. Junio C HamanoDec 22, 2013
  12. Adam SpiersDec 22, 2013
  13. Junio C HamanoDec 26, 2013
  14. Adam SpiersDec 19, 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.