3 ms·
Whats the reason to build your own command structure for filename, author, etc. instead of using the existing git tools like `git format-patch` and using `git a
by SahAssar 2y ago
Whats the reason to build your own command structure for filename, author, etc. instead of using the existing git tools like `git format-patch` and using `git am` for applying patches?
- ulrischa 2y agoI don't use git. It works via email. Or do you mean using the git commands in the email subject?
- SahAssar 2y agoI mean the format for selecting paths and so on. Git already has a standard patch format for sending changes via email and a builtin utility for applying them to a repo, so why not use that format?
- ulrischa 2y agoBut I need to have git installed. I simply want to send something to my repo via email from my smartphone.
- SahAssar 2y agoFor the mentioned workflow in chatgpt I'm guessing chatgpt can generate the email body for you in the correct format, but sure it is a step over just copy-pasting the raw text.
- arghwhat 2y agoThere is an existing, well-established patch email workflow which git natively supports. Using that, and extending it when necessary, would make more sense. See git-send-email and git-am.
- ulrischa 2y agoBut therefore I need git installed, right? I want to use it i.e. to commit some text via mail on my smartphone
- arghwhat 2y agoNo, but you need to be able to write a well-formatted diff, which is pretty much the minimum requirement for sharing changes. Emailing the entire new file every time will not work in anything but local tests as it cannot handle change conflicts. The format needs to know which parts of the file you changed, so your change does not accidentally undo other changes merged ahead of you.