From: Peter Grayson <pete@jpgrayson.net>
To: git@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@gmail.com>
Subject: [ANNOUNCE] StGit 0.19
Date: Tue, 06 Nov 2018 11:46:16 -0500 [thread overview]
Message-ID: <1541522776.3963181.1567641696.46EFA2E6@webmail.messagingengine.com> (raw)
I am pleased to announce the release of Stacked Git 0.19.
The big feature for this release is Python 3 support, but 0.19 also
contains some important bug fixes and more robust test infrastructure.
The full release notes follow.
Cheers,
Pete
----%<----
Stacked Git 0.19 released
-------------------------
StGit is a Python application providing functionality similar to Quilt
(i.e. pushing/popping patches to/from a stack) on top of Git. These
operations are performed using Git commands, and the patches are stored
as Git commit objects, allowing easy merging of the StGit patches into
other repositories using standard Git functionality.
Download: https://github.com/ctmarinas/stgit/archive/v0.19.tar.gz
Main repository: https://github.com/ctmarinas/stgit
Project homepage: http://www.procode.org/stgit/
Issue tracker: https://github.com/ctmarinas/stgit/issues
The main changes since release 0.18:
- Python 3 support. StGit supports Python 2.6, 2.7, 3.3, 3.4, 3.5, 3.6,
and 3.7. PyPy interpreters are also supported.
- Submodules are now ignored when checking if working tree is clean.
Submodules are also not included by default when refreshing a patch.
- Config booleans are now parsed similarly to git-config.
- contrib/stgit.el is now licenced with GPLv2.
- Repair handling of emails with utf-8 bodies containing latin-1
characters. Also correctly decode email headers containing quoted
encoded words.
- StGit's version is now correct/available in the release archive.
- Add continuous integration (travis-ci) and code coverage (coveralls)
support.
- Many new test cases were added.
reply other threads:[~2018-11-06 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1541522776.3963181.1567641696.46EFA2E6@webmail.messagingengine.com \
--to=pete@jpgrayson.net \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).