From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Petr Baudis <pasky@ucw.cz>
Subject: [PATCH v2 0/2] Safety for "stash save"
Date: Mon, 1 Jul 2013 14:59:09 -0700 [thread overview]
Message-ID: <1372715951-3224-1-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <20130628150532.GD12252@machine.or.cz>
The second patch is the real thing, but "ls-files --killed" needed
to be taught about submodules to avoid breaking "stash save" in a
repository with submodules, as the new safety uses it to detect what
will need to be killed (i.e. file D/F in the working tree getting
removed because we need to check out D as a file, or file D in the
working tree getting removed because we need to check out D/F as a
file) when reverting to the state in HEAD.
Junio C Hamano (1):
treat_directory(): do not declare submodules to be untracked
Petr Baudis (1):
git stash: avoid data loss when "git stash save" kills a directory
Documentation/git-stash.txt | 12 ++++++++++--
dir.c | 4 +---
git-stash.sh | 12 ++++++++++++
t/t3010-ls-files-killed-modified.sh | 23 ++++++++++++++++++++---
t/t3903-stash.sh | 18 ++++++++++++++++++
5 files changed, 61 insertions(+), 8 deletions(-)
--
1.8.3.2-798-g923e168
next prev parent reply other threads:[~2013-07-01 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 15:05 [PATCH] git stash: Avoid data loss when saving a stash Petr Baudis
2013-06-28 18:39 ` Junio C Hamano
2013-06-30 13:20 ` Petr Baudis
2013-06-30 19:14 ` Junio C Hamano
2013-07-06 14:42 ` Petr Baudis
2013-06-28 19:37 ` Junio C Hamano
2013-06-28 21:30 ` Junio C Hamano
2013-07-01 21:59 ` Junio C Hamano [this message]
2013-07-01 21:59 ` [PATCH v2 1/2] treat_directory(): do not declare submodules to be untracked Junio C Hamano
2013-07-01 21:59 ` [PATCH v2 2/2] git stash: avoid data loss when "git stash save" kills a directory Junio C Hamano
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=1372715951-3224-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).