git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: GIT <git@vger.kernel.org>
Subject: Stacked GIT 0.5
Date: Sat, 30 Jul 2005 22:32:06 +0100	[thread overview]
Message-ID: <1122759126.6865.4.camel@localhost.localdomain> (raw)

Stacked GIT 0.5 release is available from http://www.procode.org/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.

Note that StGIT is not an SCM interface on top of GIT and it expects a
previously initialised GIT repository. For standard SCM operations,
either use plain GIT commands or the Cogito tool.

For more information, see the README file in the archive.

What's new in this release (the full ChangeLog is in the archive):

      * Improved help for commands
      * 'mail' command to automatically e-mail a range of patches. The
        e-mail format is fully configurable via templates
      * 'import' command to import a GNU diff patch. The patch file can
        be a standard e-mail message or a normal file with the patch
        description at the top
      * 'pull' command to automatically advance the base of the stack
        and merge the changes into the applied patches
      * 'clean' command to delete the empty patches in a series
      * 'rename' command to change the name of a patch
      * '--range' option for the 'export' command
      * '--force' option for the 'new' command to create a patch even if
        there are local changes in the tree
      * Default templates for the 'export' and 'mail' commands
        (installed in /usr/share/stgit/templates/)
      * Bug fixes

--
Catalin

                 reply	other threads:[~2005-07-30 21:36 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=1122759126.6865.4.camel@localhost.localdomain \
    --to=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.
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).