git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Stacked GIT 0.10
Date: Sun, 11 Jun 2006 17:15:19 +0100	[thread overview]
Message-ID: <b0943d9e0606110915l767f26d0t1d2dca78c65d51ad@mail.gmail.com> (raw)

Stacked GIT 0.10 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.

The main features in this release:

    *  Handle branch names with slashes
    * Testsuite framework
    * Configurable file extensions for merge conflicts
    * 'goto' command, equivalent to 'pop --to' or 'push --to'
    * '--update' option for 'pick' to only fold the changes to files
      already in the current patch
    * '--replace' option for 'import' to replace existing patches in
      the series
    * Look for templates in ~/.stgit/templates as well
    * Allow multiple patch names on the 'push' command line
    * Classify commands in 'stg --help' output
    * Bug fixes

Acknowledgements (generated with 'git shortlog'):

Catalin Marinas:
      Allow git.checkout() to work on unmerged indexes
      Fix the added to both but different conflict
      Fix git.reset() to remove the added files
      Allow configurable file extensions for merge conflicts
      Add the --update option to pick
      Implement the 'goto' command
      Add the --replace option to import
      Fix the t1201-pull-trailing.sh test
      Show the stderr for failed GIT commands
      Generate an empty commit for the newly created patches
      Fix the add and rm commands to fail if no patch is applied
      Fix the t0001-subdir-branches.sh test
      Update the TODO file
      Release 0.10

Karl Hasselström:
      Fix infinite recursion on absolute paths
      Fix indexing error during "diff -r/"
      Explicitly specify utf-8 coding in file

Karl Hasselström:
      Don't die when there are no branches
      Handle branch names with slashes
      Tests for branch names with slashes

Pavel Roskin:
      Add .gitignore files, list generated files there
      Add a simple makefile

Yann Dirson:
      Add a testsuite framework copied from git-core
      Add list of bugs to TODO
      Add a couple of safety checks to series creation
      Make branch creation atomic
      Correctly handle refs/patches on series rename
      Fix a seriously bad interaction between .git caching and repo cloning
      Test that pulls a patch creating a file that got modified afterwards
      Exercise "stg pull" on patches just appending lines.
      Look for templates in ~/.stgit/templates as well
      Fixes to the pull testcases.
      Allow to specify multiple patch names on push command-line
      Classify commands in stg --help output.


-- 
Catalin

                 reply	other threads:[~2006-06-11 16:15 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=b0943d9e0606110915l767f26d0t1d2dca78c65d51ad@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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).