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. > >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. Prior to push, before commit, you can use reset HEAD. Following a commit, you can use reset --HARD to move the branch head back to a Commit where the add did not happen. 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.
