How do you undo an add

How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Maybe if I ask a queation a different way? What is the problem?
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.


from A_bughunter@proton.me

Sent with Proton Mail secure email.
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmc50lcJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAAtSAQCoWAIHvKlg90Ehervf3zZtd1Ls65ZW0yMZ8ms6LgKClwEAn8lO
6WSjvf58MofXRnDD88ciYBQBqfbs3v//kOiIYgA=
=O0ks
-----END PGP SIGNATURE-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

Re: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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.

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.


[A]: https://lore.kernel.org/git/20241115093214.GA1749331@coredump.intra.peff.net/#r

[B]: https://lore.kernel.org/git/xmqqr079xty7.fsf@gitster.g/T/#t

[C]: https://lore.kernel.org/all/4hiTc8Kx5yNhYuN8abv3QFJBuptM6VWZ9OKvkdZFlSI5y0zoK-lN_VHf-QCSEjllmSWvu9V-tbrvFOx17_P0Nq8UKxEcK3Rs2d02FjbYuUc=@proton.me/#r
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmc7uycJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAAUrAQDMBzGR0iQAyWfP3whiWEph0CyU+Yoveqk3jmFe7o1GMgEAm+6P
fa5TtaggX7+jcAWmRh7NvUWl6H9qFlCdxSflEQY=
=EHWY
-----END PGP SIGNATURE-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

RE: How do you undo an add

[rsbecker]

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.

Re: How do you undo an add

[Kristoffer Haugsbakk]

On Tue, Nov 19, 2024, at 00:20, rsbecker@nexbridge.com 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.
>>
>>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.

git-filter-branch? Why not `git reset --hard` with `push --force-with-lease
--force-if-includes`? Maybe I’m missing something.

> Following a commit, you can use reset --HARD to move the branch head back to a
> Commit where the add did not happen.

Yeah exactly.

-- 
Kristoffer Haugsbakk

Re: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

-----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-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

RE: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 3617 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Monday, November 18th, 2024 at 17:20, rsbecker@nexbridge.com <rsbecker@nexbridge.com> 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 #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

RE: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Tuesday, November 19th, 2024 at 02:13, Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:
> On Tue, Nov 19, 2024, at 00:20, rsbecker@nexbridge.com wrote:
> > On November 18, 2024 5:10 PM, A bughunter wrote: 
> > > 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.
> 
> git-filter-branch? Why not `git reset --hard` with `push --force-with-lease --force-if-includes`? Maybe I’m missing something.
Yes you are missing something "Without deleting any files," a bunch of irrelivent and wrong answers is SPAM because literacy is necessity for participating in any ML. 
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmc8/AgJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAGtoAQCghq6jVJrxOy2d3LX80E5gfvBKRSdl/x5UERVdELIq0gD+IjmQ
dwe5xB0oFdnlMivj1EFpVEzFYMW2GO1oCkukKgE=
=2nFM
-----END PGP SIGNATURE-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

RE: How do you undo an add

[rsbecker]

On November 19, 2024 3:59 PM, A bughunter wrote:
>On Tuesday, November 19th, 2024 at 02:13, Kristoffer Haugsbakk
><kristofferhaugsbakk@fastmail.com> wrote:
>> On Tue, Nov 19, 2024, at 00:20, rsbecker@nexbridge.com wrote:
>> > On November 18, 2024 5:10 PM, A bughunter wrote:
>> > > 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.
>>
>> git-filter-branch? Why not `git reset --hard` with `push --force-with-lease --force-
>if-includes`? Maybe I’m missing something.
>Yes you are missing something "Without deleting any files," a bunch of irrelivent
>and wrong answers is SPAM because literacy is necessity for participating in any ML.

filter-branch can be used to edit your repository if you accidentally added files
post-commit. That is why I included it in my original reply - you are free to read
the fine manuals that this team produces for more information on that and the
reset commands.

Our answers are provided as a courtesy. We are all volunteers, and I would ask
that you consider the possibility of treating the people who have spent time
in an attempt to answer your questions with a modicum of the same. Thank you.

Re: How do you undo an add

[Konstantin Ryabitsev]

On Tue, Nov 19, 2024 at 08:58:51PM +0000, A bughunter wrote:
> Yes you are missing something "Without deleting any files," a bunch of
> irrelivent and wrong answers is SPAM because literacy is necessity for
> participating in any ML. 

Please consider this your last warning. If you continue to be rude and abusive
to members of this list, I will restrict your ability to participate in
discussions here.

-K

Re: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 3568 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, November 17th, 2024 at 05:24, A bughunter <A_bughunter@proton.me> wrote:

> Maybe if I ask a queation a different way? What is the problem?
> 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.

A. You can't fully undo an 'add' because it creates a sha-object and objects are immutable.

While objects are immutable, if I do mixed mode reset switching to an old-commit under HEAD then 'add' the same files again
Q. Will it keep two copies as objects? 
A. No because when an identical file is added the object file is identical.  These become tree entries pointing to the same object. 
Q. May this overwrite the same object file because it is the same file? or because it is immutable will it reuse the old object file?
A. When an identical file is added the old object shall be _ANSWER_HERE_

I need to delete (or switch) the commit tree object to undo the 'add' (tracking) and delete the index (staged) that references the files which failed to push. The objects can be ignored because they are the same anyway when re-adding. After the tree and index are erased I can re add-commit-push.

I need to identify the tree-objects to ignore and which tree to revert to. Use git status to compare with remote. For repush the commit-id should be reverted to match with the commit-id of the remote. This resets the HEAD to reference sha-id-something for the tree-object of <old-commit-id>. Effectively untracking and leaving the git ready to re-try those failed pushs.
Q. how does git status compare if it does not ssh
use git log to find the commit-id?
A. git status uses _ANSWER_HERE_ to compare with remote.

In precaution I moved the files which had not been pushed out of the git working tree to a safer dir. ( important note: this is a precaution which the user should not need to do )  So still not sure if these files would be deleted by reset.

```--mixed
               Resets the index but not the working tree (i.e., the changed
               files are preserved but not marked for commit) and reports
               what has not been updated. This is the default action.

               If -N is specified, removed paths are marked as intent-to-add
               (see git-add(1)).

git reset --mixed <commit-id> worked but had some funny results. The results were git status showing only the file of that revert-commit marked as deleted - presumably compared the last index from before reset, however the next 285 files were not mentioned - why  . Because the status reported a match with remote I proceeded anyway not knowing why all of the files not mentioned. 
Q. After a reset why does status only mention a single file of the many files which are now ignored?
A. The reason git status only showed, after reset, a single file marked as deleted is because _ANSWER_HERE_

Then I moved the files which had not been pushed and resumed working: workaround complete. 
Use-case[C] workaround completed. bugreport[A] and question[B] remain with these more questions here in this post yet unanswered. 

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmc+QCAJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAI99AQDhOYZBjPexoTNI3Vtk1kMk3fncUaR4AwmI5cWbTJzfQAEAjGKQ
fZ6e65REGnoEoSq5Ml3czcG9tI+sEK+SI2f5ygA=
=FW62
-----END PGP SIGNATURE-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]

Re: How do you undo an add

[A bughunter]

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512




A lingering [help] question answered interspersed.

from A_bughunter@proton.me

Sent with Proton Mail secure email.

On Wednesday, November 20th, 2024 at 14:01, A bughunter <A_bughunter@proton.me> wrote:

> On Sunday, November 17th, 2024 at 05:24, A bughunter A_bughunter@proton.me wrote:

> Q. how does git status compare if it does not ssh
> use git log to find the commit-id?
> A. git status uses ANSWER_HERE to compare with remote.

Q. How does git status compare if it does not ssh? A. git status uses essentially a cache of the last value we fetched to compare with remote. See also "is comparing your branch with the local tracking branch we have, refs/remotes/origin/main. It doesn't touch the network, and that tracking branch is essentially a cache of the last value we fetched." ( https://lore.kernel.org/git/20241205201952.GB2635755@coredump.intra.peff.net/ )
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmdSFSIJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAIzzAQCCC3GPjxGsJu/OE51LuIBbmhZ7o3FwxuRo61m9l4V0rAEAjn82
cLmBej/67p7s3eYLzQdtqfBP1LQz3bloa9uXjQE=
=5q/u
-----END PGP SIGNATURE-----

[-- Attachment #2: publickey - A_bughunter@proton.me - 0x66540805.asc --]
[-- Type: application/pgp-keys, Size: 653 bytes --]

[-- Attachment #3: publickey - A_bughunter@proton.me - 0x66540805.asc.sig --]
[-- Type: application/pgp-signature, Size: 119 bytes --]