5/8/2023 0 Comments Webtrees vs phpgedview![]() The former would have forced deleted the files from Folder2 from both the staging area as well as my working tree (something I did not intend/want). The latter would have only unstaged the files but left them in my working tree (something that is precisely what I would have wanted.) The number of files under Folder2 are rather large and a due diligence check on Folder2's contents manually on my machine seems to reveal nothing amiss in terms of missing files from my working tree. Yet, just to be absolutely sure, is there a way to list all of the git commands ever issued under a repository from the beginning of time? Note that I am not asking for a history of commands I have issued from the terminal command line. This would be available in a powershell history or bash shell history.Ī previous question of exactly this issue is available here. However, the question is about 10 years old and the highest voted answer there suggests to use git reflog. However, that seems to give history in terms of commits. I am looking more for the exact git commands that I have executed. In any case, install should not make any changes to a lockfile, so there shouldn't be anything to "revert" from an install but deleting the installed files. If the lockfile does not originally exist, then it will be created. If some other plugin (e.g Symfony Flex) makes changes to your existing files during the process, you'd better have the project on top of a version control system, in which case reverting is managed by VCS, not of composer.Īs my intention is to rollback to the state that did not have any package installed but only files: composer.lock and potentially composer.jsonįor you to be able to run composer install at all, you need at the very least composer.json to exist. install reads from the lockfile ( composer.lock), but requires the JSON configuration file to exist as well. If the lockfile does not exist, update will be run instead and the lockfile will be created. It removes packages from composer.json, as require adds them. There is no opposite of install, as it does not make much conceptual sense. ![]() NOTICE: 'suricata' packaging is maintained in the 'Git' version control system at: If one needs to delete the installed project. Get:3 bionic/universe suricata 3.2-2ubuntu3 (diff) ĭpkg-source: info: extracting suricata in suricata-3.2ĭpkg-source: info: unpacking suricata_3.2.ĭpkg-source: info: unpacking suricata_3.ĭpkg-source: info: applying reproducible.patchĭpkg-source: info: applying debian-default-cfg.patchĭpkg-source: info: applying optional-hyperscan.patch Get:2 bionic/universe suricata 3.2-2ubuntu3 (tar) Get:1 bionic/universe suricata 3.2-2ubuntu3 (dsc) To retrieve the latest (possibly unreleased) updates to the package. suricata_3.2-2ubuntu3.dscĪnd then it hangs forever. Highly uninformative.Īlso, in the stackoverflow post in the link above someone talks about protocols. ![]()
0 Comments
Leave a Reply. |