-
Notifications
You must be signed in to change notification settings - Fork 82
Deleted files are not absorbed #189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Duplicate of #46. As an aside @toy, which version are you using? 0.8.0 should emit a clear message about this, including the phrase "Added, removed, or renamed files cannot be automatically absorbed.". Is this the case for you?
|
I missed #46, as deletion only mentioned in later comment. I understand that it may be a "dangerous" option, but I'd argue that at least if a file was only created on a branch (so no changes after creation) and then staged for deletion, then it would be nice to have an option to auto absorb. Same for creating following deletion as described in #46. Renames are probably handleable only if previous commit touching that file was also renaming it. Core git allows to shoot oneself in the foot, but also in most cases to get the previous version of that foot Version wise I have 0.7.0 from macports |
yes, let's keep this as a duplicate of 46 please. and it doesn't surprise me that you don't have 0.8 yet, most distributions are probably catching up to that |
I tried the tool and noticed right away that it was not able to handle deletion of file, here are commands to reproduce
The text was updated successfully, but these errors were encountered: