From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH 0/5] Make push and refresh subdirectory safe
Date: Mon, 08 Oct 2007 01:24:35 +0200 [thread overview]
Message-ID: <20071007231949.13070.49517.stgit@yoghurt> (raw)
This series makes push and refresh safe to use from subdirectories, by
using the infrastructure of the first patch to cd to the top of the
worktree.
As stated in the commit messages, this may not be an optimal long-term
solution, but we need to fix this quick. And the infrastructure isn't
good only for cd'ing to the top of the worktree.
This series is also available from
git://repo.or.cz/stgit/kha.git safe
---
Karl Hasselström (5):
Make "stg refresh" subdirectory safe
New test: try "stg refresh" in a subdirectory
Make "stg push" subdirectory safe
New test: Try "stg push" in a subdirectory
Infrastructure for current directory handling
stgit/commands/add.py | 1 +
stgit/commands/applied.py | 1 +
stgit/commands/assimilate.py | 1 +
stgit/commands/branch.py | 1 +
stgit/commands/clean.py | 1 +
stgit/commands/clone.py | 1 +
stgit/commands/commit.py | 1 +
stgit/commands/common.py | 68 ++++++++++++++++++++++++++++++++++++++++++
stgit/commands/copy.py | 1 +
stgit/commands/delete.py | 1 +
stgit/commands/diff.py | 1 +
stgit/commands/edit.py | 1 +
stgit/commands/export.py | 1 +
stgit/commands/files.py | 1 +
stgit/commands/float.py | 1 +
stgit/commands/fold.py | 1 +
stgit/commands/goto.py | 1 +
stgit/commands/hide.py | 1 +
stgit/commands/id.py | 1 +
stgit/commands/imprt.py | 1 +
stgit/commands/init.py | 1 +
stgit/commands/log.py | 1 +
stgit/commands/mail.py | 1 +
stgit/commands/new.py | 1 +
stgit/commands/patches.py | 1 +
stgit/commands/pick.py | 1 +
stgit/commands/pop.py | 1 +
stgit/commands/pull.py | 1 +
stgit/commands/push.py | 1 +
stgit/commands/rebase.py | 1 +
stgit/commands/refresh.py | 1 +
stgit/commands/rename.py | 1 +
stgit/commands/resolved.py | 1 +
stgit/commands/rm.py | 1 +
stgit/commands/series.py | 1 +
stgit/commands/show.py | 1 +
stgit/commands/sink.py | 1 +
stgit/commands/status.py | 1 +
stgit/commands/sync.py | 1 +
stgit/commands/top.py | 1 +
stgit/commands/unapplied.py | 1 +
stgit/commands/uncommit.py | 1 +
stgit/commands/unhide.py | 1 +
stgit/main.py | 2 +
t/t1205-push-subdir.sh | 55 ++++++++++++++++++++++++++++++++++
t/t2300-refresh-subdir.sh | 27 +++++++++++++++++
46 files changed, 194 insertions(+), 0 deletions(-)
create mode 100755 t/t1205-push-subdir.sh
create mode 100755 t/t2300-refresh-subdir.sh
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next reply other threads:[~2007-10-07 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 23:24 Karl Hasselström [this message]
2007-10-07 23:24 ` [StGit PATCH 1/5] Infrastructure for current directory handling Karl Hasselström
2007-10-07 23:24 ` [StGit PATCH 2/5] New test: Try "stg push" in a subdirectory Karl Hasselström
2007-10-07 23:24 ` [StGit PATCH 3/5] Make "stg push" subdirectory safe Karl Hasselström
2007-10-07 23:25 ` [StGit PATCH 4/5] New test: try "stg refresh" in a subdirectory Karl Hasselström
2007-10-07 23:25 ` [StGit PATCH 5/5] Make "stg refresh" subdirectory safe Karl Hasselström
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=20071007231949.13070.49517.stgit@yoghurt \
--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.
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).