From: Catalin Marinas <catalin.marinas@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Karl Wiberg <kha@treskal.com>
Subject: [ANNOUNCE] Stacked Git 0.15-rc3
Date: Sun, 13 Sep 2009 17:01:41 +0100 [thread overview]
Message-ID: <b0943d9e0909130901n7655db7av71471148117711d3@mail.gmail.com> (raw)
The third release candidate for StGit 0.15 is available from the
git://repo.or.cz/stgit.git or http://download.gna.org/stgit/. Bugs can
be reported on the Git mailing list or via the project bugs page
(https://gna.org/bugs/?group=stgit).
StGit is a Python application providing similar functionality 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.
Unless there are major issues, the aim is for this to be the last
release candidate before 0.15.
The main changes since release 0.15-rc2:
- 'stg import' command fixes to allow the importing of 'git show' output
and also support the -pN option for stripping leading slashes from
diff paths. The author date when importing e-mails is also preserved
- Generate binary diffs by default when exporting patches
- Other bug-fixes
Acknowledgements:
Catalin Marinas (7):
Add stg-build, stg-dbg and RELEASENOTES to the MANIFEST.in file
Merge commit 'kha/safe'
Import git show output easily
Merge commit 'kha/safe'
Add import -p option
Preserve the given author date during import
Generate binary diffs by default
David Kågedal (1):
Escape patch name when creating regexp
Karl Wiberg (2):
When reading a config value, pick the last value, not the first
squash: Make commit message editing more convenient
--
Catalin
reply other threads:[~2009-09-13 16:01 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0943d9e0909130901n7655db7av71471148117711d3@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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.
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 NNTP newsgroup(s).