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

Re: DEVEL: Help with feature implementation

From
ABAiyee Bee <shane.880088.supw@gmail.com>
Date
Jan 19, 2021, 05:38 UTC
Message-ID
<C8MW4U7TN2CA.2NMNG05BE2J97@localhost>
In-Reply-To
<5e5ece7c-3f34-caa1-db87-084b42c1cb62@gmail.com>
Hi Derrick and Junio!

Thanks for confirming my suspicions, that there isn't existing apparatus for doing this, and a new bit can be added as a flag. Thanks for the *pointers, I'll try working it out! With Antonio, in fact, since they'd need the same thing for implementing the opposite feature.

As for the justification, to elaborate on what I said in the opening mail:

This option would be pretty useful when used with diff options, to see how much two forks have diverged. I recently wanted to compare two long-running forks of a project and see how far they have diverged. I used the options: --simplufy-by-decoration --decorate-refs="refs/remotes/*/main" -p

But currently with this history simplification, the diffs for both divergent histories will be created against the last "relevant" (decorated) commit instead of the last common ancestor, which creates pretty useless diffs with a lot of intersection between them.

You're right that the option doesn't sound very useful when thought of in regards to history limiting by path, but IMO it's pretty useful in cases like these, when you use simplify to get an 'overview' of the history.

Also sorry for the blank/duplicate emails everyone! My email client seems to be misbehaving, largely because I tried to tinker with it :P

- Aiyee Bee
Previous: Derrick StoleeNext: Aiyee Bee
Message 14 of 16 in “DEVEL: Help with feature implementation”
  1. Aiyee BeeJan 18, 2021
  2. Antonio RussoJan 18, 2021
  3. Derrick StoleeJan 18, 2021
  4. Aiyee BeeJan 18, 2021
  5. Junio C HamanoJan 18, 2021
  6. Aiyee BeeJan 18, 2021
  7. Aiyee BeeJan 18, 2021
  8. Derrick StoleeJan 18, 2021
  9. Antonio RussoJan 19, 2021
  10. Junio C HamanoJan 19, 2021
  11. Antonio RussoJan 19, 2021
  12. Derrick StoleeJan 20, 2021
  13. Derrick StoleeJan 19, 2021
  14. Aiyee BeeJan 19, 2021
  15. Aiyee BeeJan 19, 2021
  16. Antonio RussoJan 19, 2021

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.