| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
Put the point at the beginning of the file before doing a search for
the message body.
* git-email.el (git-email--compose-email):
|
|
|
|
|
|
|
|
|
|
| |
These changes were made to make git-email work better with Magit (the
following commit will cover this).
ARGS is a string of arguments passed to "git format-patch", RANGE is
the range of commits to create patches from. If prefix argument KEEP
is specified, keep the generated patches, be default they will be
deleted like with "git send-email".
|
|
|
|
| |
`git-email-send-email' will take a list of files as an argument.
|
|
|
|
|
| |
The cursor will be placed at the "to" header if it is empty when
composing a message.
|
|
|
|
|
|
| |
This is better handled by the piem[0] package.
[0]: https://git.kyleam.com/piem
|
|
|
|
|
|
|
|
| |
Modularize `git-email-apply-patch', this way other functions can also
use `git-email--get-project'.
* git-email.el (git-email--get-project):
(git-email-apply-patch):
|
|
|
|
|
|
| |
Use 0.2.0 instead of 1.0.0
* git-email.el:
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
|
|
|
| |
Explicitly ask for the version number (-v option) if
`git-email-format-patch' has been called the a prefix argument.
* git-email.el (git-email--compose-email):
(git-email-format-patch):
|
|
|
|
| |
* git-email.el:
|
|
|
|
| |
* git-email.el:
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
| |
* git-email.el (git-email-format-patch): Delete the patches generated by
'git format-patch' after sending the emails.
|
|
|
|
|
|
| |
An error will the thrown otherwise.
* git-email.el (git-email--log-get-revision):
|
|
|
|
|
|
|
|
| |
Keep line width under 80.
* git-email.el (git-email--fontify-using-faces):
(git-email--compose-email):
(git-email-format-patch):
|
|
|
|
|
|
|
|
|
| |
* git-email.el (git-email--extract-diff):
(git-email--fontify-diff):
(git-email--fontify-using-faces):
(git-email--compose-email):
(git-email--minibuffer-get-revision):
(git-email-format-patch):
|
|
|
|
|
|
|
|
|
|
|
|
| |
Let the user specify a list of functions to run to get the desirable
revision and fallback to the minibuffer.
* git-email.el (git-email-revision-command):
(git-email-get-revision-functions):
(vc-dir-current-file):
(git-email--get-revision):
(git-email--log-get-revision):
(git-email-format-patch):
|
|
|
|
|
|
|
|
| |
Let the user specify the 'git log' command to run, this wont really play
well with the current colorization regex.
* git-email.el (git-email-revision-command):
(git-email--get-revision):
|
|
|
|
|
|
|
| |
If in `log-view-mode', get the revision under point instead of asking
for a revision
* git-email.el (git-email-format-patch):
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
|
|
| |
git-email--get-filename => git-email--get-files
* git-email.el (git-email--get-filenames):
(git-email-send-email):
|
|
|
|
|
|
|
| |
Don't depent on `log-view-mode' to be loaded.
* git-email.el (git-email-revision-face):
(git-email--get-revision):
|
|
|
|
|
|
|
|
|
|
|
| |
Users can add their own function to `git-email-get-files-functions' to
get a list of files to send as patches.
* git-email.el (git-email-get-files-functions):
(git-email--dired-files):
(git-email--vc-dir-files):
(git-email--ibuffer-files):
(git-email--get-filenames):
|
|
|
|
|
|
|
|
|
|
| |
The user can supply a custom function and command to used instead of the
default ones.
* git-email.el (git-email-apply-patch-function):
(git-email-apply-patch-command):
(git-email--shell-command-on-body):
(git-email-apply-patch):
|
|
|
|
|
|
|
| |
* git-email.el (git-email--check-file):
(git-email--get-revision):
(git-email-apply-patch):
(git-email-send-email):
|
|
|
|
|
|
| |
* git-email.el (git-email-revision-limit):
(git-email--get-revision):
(git-email-format-patch):
|
|
|
|
|
|
|
| |
Throw an error if the selected files aren't valid patch files.
* git-email.el (git-email--check-file):
(git-email--get-filenames):
|
|
|
|
|
|
|
|
| |
If the current major mode isn't supported, ask the user for a file in
the minibuffer.
* git-email.el (git-email--minibuffer-file):
(git-email--get-filenames):
|
|
|
|
|
|
|
| |
* git-email.el (git-email--dired):
(git-email--vc-dir):
(git-email--ibuffer):
(git-email--get-filenames):
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
|
|
|
| |
* git-email.el (dired-get-filename):
(dired-map-over-marks):
(ibuffer-get-marked-buffers):
(vc-dir-marked-files):
(vc-dir-current-file):
|
|
|
|
|
| |
* git-email.el (git-email-send-email-function):
(git-email-send-all):
|
|
|
|
| |
* git-email.el (git-email-apply-patch):
|
|
|
|
|
|
| |
Add description for `git-email-format-patch'.
* git-email.el:
|
|
|
|
|
|
|
|
|
| |
This lets the user generate patches and automatically compses an email
for each patch.
* git-email.el (git-email-format-patch-default-args):
(git-email-format-patch-extra-args):
(git-email-format-patch):
|
|
|
|
|
|
| |
Explain some parts in more detail.
* git-email.el (git-email--compose-email):
|
|
|
|
|
|
|
|
|
| |
Update docstrings for types for hooks and run them before and after every
`git-email--compose-email' call.
* git-email.el (git-email-pre-compose-email-hook):
(git-email-post-compose-email-hook):
(git-email-send-email):
|
|
|
|
|
|
|
|
|
| |
Use symbols instead of strings.
* git-email.el (git-email-headers):
(git-email-send-email):
(git-email--format-headers):
(git-email--compose-email):
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The key of the alist has to be a symbol and not a string. This fixes
the formatting of the 'references' header.
Remove the redundant functions for setting `message-header-format-alist'.
* git-email.el (git-email-pre-compose-email-hook):
(git-email-post-compose-email-hook):
(git-email--set-message-header-format):
(git-email--reset-message-header-format):
(git-email-send-email):
(git-email--format-headers):
(git-email--remove-subject):
(git-email--compose-email):
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
|
|
|
|
| |
Some mail clients will automatically pre-populate the message buffer
with the users signature, inserting the diff at the end of the file
would then mess up the formatting. This patch make it so that the diff
is inserted after '--text follows this line--' or a pgp attachment.
* git-email.el (git-email--compose-email):
|
|
|
|
|
|
| |
Put the cursor at the subject header if the message is a cover letter.
* git-email.el (git-email--compose-email):
|
|
|
|
|
|
|
| |
Put the cursor at the beginning of the body of the message instead of at
the end.
* git-email.el (git-email--compose-email):
|
|
|
|
| |
* git-email.el:
|
|
|
|
|
|
|
|
| |
Be more consistent with the other variables.
git-email-compose-message-function => git-email-compose-email-function
* git-email.el:
|
|
|
|
|
|
| |
Remove redundant docs regarding message headers.
* git-email.el (git-email-headers):
|
|
|
|
|
|
|
|
|
|
|
| |
This is more of a hack for setting `message-header-format-alist' so that
the 'References' header gets parsed correctly.
* git-email.el (git-email-pre-compose-email-hook):
(git-email-post-compose-email-hook):
(git-email--set-message-header-format):
(git-email--reset-message-header-format):
(git-email-send-email):
|
|
|
|
|
|
| |
Add project.el as a dependency
* git-email.el:
|