-
Notifications
You must be signed in to change notification settings - Fork 66
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
stgit.el update #521
Comments
Hi @nicolas-graves. Thanks for working on packaging StGit for Guix. The state of StGit's various emacs packages is not great. You're right that |
Well, I'm using it for my daily(ish) work, so while the bindings are not complete, I'd say it's definitely a usable subset. I've never used stgit,el, so can't really say anything about how that compares to magit-stgit, though :) |
Thanks for that perspective, @tohojo--that's helpful. So perhaps it would make sense to tag the latest Do we think that would be a 2.2.0 or 3.0.0 tag? I'm not super familiar with how MELPA works, but it appears from looking at the melpa recipe for StGit that if we were to push a new |
Yeah, I agree that tagging a new version makes sense. No strong opinion about which version number to go with. I suppose the switch to transient could be occasion enough to go for the big 3.0? :) No idea how melpa works, but from just looking at that recipe I guess you're right? |
I'll create a new 3.0.0 tag for |
I tried using stgit.el today and immediatley ran into symbol void: git-status, which i guess comes from the venerable git.el from git/contrib/emacs (well, used to to come from up until several years ago) |
Hi StGit!
I was trying to package stgit.el for Guix, and I noticed tere is quite some cleaning to do on
stgit.el
, I have the following warnings on compilation:log.txt
I also wondered about the status of the package, I've seen that
magit-stgit
has been updated and I'm wondering if the statementas found on MELPA stable still holds true, or if
magit-stgit
is the one recommended now (maybe we should make a release for MELPA stable ?).The text was updated successfully, but these errors were encountered: