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

Re: How do you undo an add

From
ABA bughunter <a_bughunter@proton.me>
Date
Nov 19, 2024, 20:49 UTC
Message-ID
<gEGJ85bqla-NTL4ZJ1yt-zAAIaIYhp0s7hy3EJNmb5rF08NptfrexXMHZO6p4vZ7i6atRVsB09dlJ2z4hEXtOhH8MlqVpSg_8GlBDn6GiGM=@proton.me>
In-Reply-To
<89DnJJL6nbYjQW9N8CtejlqbnzPDiH7iKd-3zKFY8oQezk1rRYbjH5WkKdrVPYPQQsKPhMpd3IcBet7ZBD4U3HSSoXk6rVXIMWPaG4hAj1g=@proton.me>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
After looking into filter-branch here is what I found out. from the docs:

WARNING git filter-branch has a plethora of pitfalls that can produce non-obvious manglings of the intended history rewrite (and can leave you with little time to investigate such problems since it has such abysmal performance). These safety and performance issues cannot be backward compatibly fixed and as such, its use is not recommended. Please use an alternative history filtering tool such as git filter-repo. If you still need to use git filter-branch, please carefully read SAFETY (and PERFORMANCE) to learn about the land mines of filter-branch, and then vigilantly avoid as many of the hazards listed there as reasonably possible. ( https://git-scm.com/docs/git-filter-branch )

So here a git beginner, myself is cornered into navigating a "minefield". Illuminated language that git is full of undocumented known bugs. I see now what this facade of rejecting bugreports is about: it  seem's about the bugreport recievers do dance around the jargon term "bug" in favor of various possibly more accurate 'illuminations' however as I have put in plain english a bug is a defect. 
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmc8+dYJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu 8pkAAAxwAP9ISjq2ja8Oc+BzmVTd39zFQ7G/fIuqRPvPhEoK9w5uIAD+Jtia wSnZYAEkEIPi7wAFU1wBhsgp6eU0Z5OMZhQM0Aw= =2LbM -----END PGP SIGNATURE-----

Previous: A bughunter
Message 11 of 11 in “How do you undo an add”
  1. A bughunterNov 17, 2024
  2. A bughunterNov 18, 2024
  3. rsbecker@nexbridge.comNov 18, 2024
  4. Kristoffer HaugsbakkNov 19, 2024
  5. A bughunterNov 19, 2024
  6. A bughunterNov 19, 2024
  7. rsbecker@nexbridge.comNov 19, 2024
  8. Konstantin RyabitsevNov 20, 2024
  9. A bughunterNov 20, 2024
  10. A bughunterDec 5, 2024
  11. A bughunterNov 19, 2024

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.