From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: StGIT experimental branches updated
Date: Mon, 3 Sep 2007 02:20:29 +0200 [thread overview]
Message-ID: <20070903002029.GA31957@diana.vm.bytemark.co.uk> (raw)
I've added the three patches I just sent out. That's all, since no one
else seems to be working. :-)
Plus, I've renamed the branches to "safe" and "experimental", since
that's what they're all about.
-+-
The following changes since commit 18669b744dbc40df9ce025f3db44a28f7aba29ff:
Catalin Marinas (1):
Add the '--exclusive' option to 'uncommit'
are available in the git repository at:
git://repo.or.cz/stgit/kha.git safe
David Kågedal (2):
Add basic test for stg status
Cleanup tree_status and use -z
Karl Hasselström (5):
Write warnings and errors to stderr if not on a terminal
Don't fail just because a subprocess wrote stuff to stderr
Let "stg status" ignore empty directories
Allow "stg add" when we have no stack
Test "stg status" more thoroughly
Pavel Roskin (2):
Use --force to overwrite python files
Fix refresh -es
Makefile | 2 +-
stgit/commands/add.py | 3 -
stgit/commands/patches.py | 2 +-
stgit/commands/refresh.py | 2 +-
stgit/git.py | 25 +++++----
stgit/out.py | 11 +++-
stgit/run.py | 5 ++-
stgit/stack.py | 3 +-
t/t0002-status.sh | 125 +++++++++++++++++++++++++++++++++++++++++++++
9 files changed, 156 insertions(+), 22 deletions(-)
create mode 100755 t/t0002-status.sh
-+-
The following changes since commit eda4068ff351143504a416393514b9fc57fb7fae:
Karl Hasselström (1):
Test "stg status" more thoroughly
are available in the git repository at:
git://repo.or.cz/stgit/kha.git experimental
David Kågedal (6):
Split git.merge into two functions
Leave working dir and index alone after failed (conflicting) push
Added a test case to check what happens when push finds a conflict
Simplify merge_recursive
Use the output from merge-recursive to list conflicts
Ask git about unmerged files
Karl Hasselström (12):
Compute patch appliedness from commit DAG
Test the new DAG appliedness machinery
Fix bash completion after the DAG appliedness patch
Speed up the appliedness test
Speed up the discovery of uninteresting commits
Speed up appliedness check during patch creation
Don't traverse the whole DAG when looking for uninteresting commits
Find uninteresting commits faster for special cases
Optimize uninterestingness checks for rebase
Better error message if merge fails
Fix "stg resolved" to work with new conflict representation
Merge branch 'conflict'
contrib/stgit-completion.bash | 15 +-
stgit/commands/commit.py | 8 +-
stgit/commands/common.py | 24 +--
stgit/commands/float.py | 2 +-
stgit/commands/imprt.py | 2 +-
stgit/commands/pick.py | 2 +-
stgit/commands/refresh.py | 2 +-
stgit/commands/resolved.py | 19 +-
stgit/commands/sync.py | 2 +-
stgit/git.py | 74 ++++--
stgit/gitmergeonefile.py | 99 ++++----
stgit/stack.py | 574 +++++++++++++++++++++++++++++++++--------
t/t0002-status.sh | 3 -
t/t1203-push-conflict.sh | 70 +++++
t/t3000-git-interop.sh | 60 +++++
t/t4000-upgrade.sh | 6 +
16 files changed, 730 insertions(+), 232 deletions(-)
create mode 100755 t/t1203-push-conflict.sh
create mode 100755 t/t3000-git-interop.sh
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next reply other threads:[~2007-09-03 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 0:20 Karl Hasselström [this message]
2007-09-03 8:29 ` StGIT experimental branches updated Catalin Marinas
2007-09-03 9:01 ` Karl Hasselström
2007-09-03 9:32 ` Catalin Marinas
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=20070903002029.GA31957@diana.vm.bytemark.co.uk \
--to=kha@treskal.com \
--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).