Skip to content
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

Ongoing development of git-wip-mode? #25

Open
occidens opened this issue Apr 21, 2015 · 1 comment
Open

Ongoing development of git-wip-mode? #25

occidens opened this issue Apr 21, 2015 · 1 comment

Comments

@occidens
Copy link

@bartman, are you planning to keep maintaining git-wip-mode, or is it deprecated in favor of magit-wip as suggested in #14?

The reason I ask is that I made some enhancements to git-wip-mode before Iearning about magit-wip. One addresses #21, and another fixes the problem that git-wip-after-save sends the message "Wrote and git-wip'd" even if the asynchronous process calling git-wip fails. I can send over a pull request if there is interest in ongoing development, though in that case, it would be good to take action on PR #12, since my changes affect some of the same functions.

Thanks.

@bartman
Copy link
Owner

bartman commented Apr 22, 2015

Thanks for your interest Will.

I am not an emacs user so git-wip-mode is something I cannot comment on.

I will leave git-wip-mode.el in the repo, until such time that someone
suggests to me that it's completely a waste of time and I should remove it.

-Bart

On Tue, Apr 21, 2015 at 4:52 PM, William West notifications@github.com
wrote:

@bartman https://github.com/bartman, are you planning to keep
maintaining git-wip-mode, or is it deprecated in favor of magit-wip as
suggested in #14 #14?

The reason I ask is that I made some enhancements to git-wip-mode before
Iearning about magit-wip. One addresses #21
#21, and another fixes the
problem that git-wip-after-save sends the message "Wrote and git-wip'd"
even if the asynchronous process calling git-wip fails. I can send over a
pull request if there is interest in ongoing development, though in that
case, it would be good to take action on PR #12
#12, since my changes affect
some of the same functions.

Thanks.


Reply to this email directly or view it on GitHub
#25.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants