-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Monday, November 18th, 2024 at 17:20, rsbecker@xxxxxxxxxxxxx <rsbecker@xxxxxxxxxxxxx> wrote: > On November 18, 2024 5:10 PM, A bughunter wrote: > > > BROAD OVERVIEW > > > > bugreport[A], question[B] and use-case[C]. These are all related but separate > > threads for the purposes as labled. Please do not cross-post or cross-quote. Focus > > on productivity and solving these. You are welcomed to view and participate in all of > > these as I contribute more. I appreciate your understanding. > > use-case[C] - git question (short) rephrase with use-case added. > > > > ADD, ADD, ADD why cant they get that: ADD. ADD tracks files for commit. It's > > already been commit : push failed. Failed pushes piled up. I need them untracked. > > How do you undo an add ( many adds): simple question. Without deleting any files, > > to repush 1 by 1. > > > Once you have pushed an added file, your only option is filter-branch to prune out the > invalid content. I will look into filter-branch. I will let you, rsbecker, know if it works for the purposes of displaying the solution to the entire git community. If you have any more relevent specifics about the use of filter-branch you are welcome to post. Just as you form a response, to focus, pin my question in front of you as you write about filter-branch. The rest of this slightly peaves me because none of it has to do with the TOPIC my question. > Prior to push, before commit, you can use reset HEAD. This delete's files and if it is the only option in my given situation it does CONFIRM my bugreport[A]. > Following a commit, you can use reset --HARD to move the branch head back to a > Commit where the add did not happen. Seek grace. > If I did not understand your situation, I apologize. > > > I suspect the answer is: "you can't - git provides no means to do so" - a defect, bug > > as we call it. The answer to this use-case question likely will confirm my bugreport > > and I get the feeling this is why they will not answer the question they do not want > > to accept my bugreport and have a bad spirit to argue. The excuses they give for this > > will be that it is not typical: This can normally be solved by repushing. However it is > > still a defect and in my use-case there is a slow or intermittent connection and no > > sha-backups yet because this is the initial creation of a repo. > > > > The above question is a use-case[C] seeking how to undo without deleting files. > > There shouldn't be any need to know a use-case in order to answer a technical > > question. I am open to discuss my use-case on this thread. The use-case if of this > > repo github.com/freedom-foundation/kjbible > > > > My original bug report is that the user " may be cornered into delete files" > > bugreport[A] Summary as of 20241117 brian does not believe it's a bug and begins > > chattering to Peff about how to fix the bug "There are Git-level keepalives during the > > similar compression operation". > > > > The full question[B] which is a child of the bugreport[A] is here. Summary as of > > 20241117 my question was mostly sidestepped and spammed whilst the thread > > devolved into a political drama about code_of_conduct. I am not open to discuss > > my use-case on this thread. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmc87P0JkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu 8pkAAPviAP4uP8OEMcmzOHpuCEaByLjVudqKuqPNzI2s/UXBZHNoYwD+Kg3m U9IuHANF21RXERRYLiX+mjcQzLEdmov/dpjXOw4= =vuRu -----END PGP SIGNATURE-----
Attachment:
publickey - A_bughunter@proton.me - 0x66540805.asc
Description: application/pgp-keys
Attachment:
publickey - A_bughunter@proton.me - 0x66540805.asc.sig
Description: PGP signature
