From: Jens Lehmann <Jens.Lehmann@web.de>
To: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
Jonathan Nieder <jrnieder@gmail.com>, Jeff King <peff@peff.net>
Subject: [PATCH 00/14] Add submodule test harness
Date: Sun, 15 Jun 2014 18:56:09 +0200 [thread overview]
Message-ID: <539DD029.4030506@web.de> (raw)
This is the series I sought feedback for some time ago in gmane/$245048. It
took longer than I expected to finish this series because I had to diagnose
the test failures I saw with some of the ten commands I added since then.
They boiled down to four different inconsistencies in Git's handling of new
or removed submodules. Sometimes no empty directory is created for a new
submodule. stash and cherry-pick seem to use wrong submodule ignore settings
("all" instead of "dirty"), so they overlook submodule changes. And merge
behaves strange when a submodule is removed, as it tries to merge new tracked
files with those remaining from the submodule. This series only documents
these issues (which most probably didn't cause any real world problems until
now because adding and removing submodules wasn't well supported anyway).
The first patch adds a simple helper function to the test lib which makes
it easier to test for an empty submodule directory.
The second patch contains the heavy lifting, it adds the test framework for
switching submodules. Currently only transitions without merge conflicts are
tested for, I intend to add others producing merge conflicts in a follow-up
series.
The other twelve patches use the framework to test all relevant work tree
manipulating commands. In addition to the two general problems documented
in the second patch some patches add known failures for problems of some
commands/actions to be fixed in later patches.
The only work tree changing command I didn't cover here is checkout-index, as
that updates the work tree to the content of the index but doesn't remove any
formerly tracked files, which means it doesn't do a full transition from one
commit to another. If I overlooked another command, please speak up so I can
include it too.
Jens Lehmann (14):
test-lib: add test_dir_is_empty()
submodules: Add the lib-submodule-update.sh test library
checkout: call the new submodule update test framework
apply: add t4137 for submodule updates
read-tree: add t1013 for submodule updates
reset: add t7112 for submodule updates
bisect: add t6041 for submodule updates
merge: add t7613 for submodule updates
rebase: add t3426 for submodule updates
pull: add t5572 for submodule updates
cherry-pick: add t3512 for submodule updates
am: add t4255 for submodule updates
stash: add t3906 for submodule updates
revert: add t3513 for submodule updates
t/lib-submodule-update.sh | 670 +++++++++++++++++++++++++++++++++++++++
t/t1013-read-tree-submodule.sh | 12 +
t/t2013-checkout-submodule.sh | 5 +
t/t3426-rebase-submodule.sh | 46 +++
t/t3512-cherry-pick-submodule.sh | 13 +
t/t3513-revert-submodule.sh | 32 ++
t/t3906-stash-submodule.sh | 24 ++
t/t4137-apply-submodule.sh | 20 ++
t/t4255-am-submodule.sh | 21 ++
t/t5572-pull-submodule.sh | 74 +++++
t/t6041-bisect-submodule.sh | 32 ++
t/t7112-reset-submodule.sh | 14 +
t/t7613-merge-submodule.sh | 19 ++
t/test-lib-functions.sh | 11 +
14 files changed, 993 insertions(+)
create mode 100755 t/lib-submodule-update.sh
create mode 100755 t/t1013-read-tree-submodule.sh
create mode 100755 t/t3426-rebase-submodule.sh
create mode 100755 t/t3512-cherry-pick-submodule.sh
create mode 100755 t/t3513-revert-submodule.sh
create mode 100755 t/t3906-stash-submodule.sh
create mode 100755 t/t4137-apply-submodule.sh
create mode 100755 t/t4255-am-submodule.sh
create mode 100755 t/t5572-pull-submodule.sh
create mode 100755 t/t6041-bisect-submodule.sh
create mode 100755 t/t7112-reset-submodule.sh
create mode 100755 t/t7613-merge-submodule.sh
--
2.0.0.275.gc479268
next reply other threads:[~2014-06-15 16:56 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 16:56 Jens Lehmann [this message]
2014-06-15 16:57 ` [PATCH 01/14] test-lib: add test_dir_is_empty() Jens Lehmann
2014-06-16 22:05 ` Junio C Hamano
2014-06-17 16:47 ` Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 16:58 ` [PATCH 02/14] submodules: Add the lib-submodule-update.sh test library Jens Lehmann
2014-06-16 22:49 ` Junio C Hamano
2014-06-17 17:33 ` Jens Lehmann
2014-06-17 18:44 ` Junio C Hamano
2014-06-17 20:46 ` Jens Lehmann
2014-06-17 21:05 ` Junio C Hamano
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-20 17:31 ` Junio C Hamano
2014-07-01 21:24 ` [PATCH v3 " Jens Lehmann
2014-06-15 16:58 ` [PATCH 03/14] checkout: call the new submodule update test framework Jens Lehmann
2014-06-15 16:59 ` [PATCH 04/14] apply: add t4137 for submodule updates Jens Lehmann
2014-06-15 16:59 ` [PATCH 05/14] read-tree: add t1013 " Jens Lehmann
2014-06-15 17:00 ` [PATCH 06/14] reset: add t7112 " Jens Lehmann
2014-06-15 17:01 ` [PATCH 07/14] bisect: add t6041 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:01 ` [PATCH 08/14] merge: add t7613 " Jens Lehmann
2014-06-15 17:02 ` [PATCH 09/14] rebase: add t3426 " Jens Lehmann
2014-06-16 9:57 ` Eric Sunshine
2014-06-17 17:41 ` Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:02 ` [PATCH 10/14] pull: add t5572 " Jens Lehmann
2014-06-15 17:03 ` [PATCH 11/14] cherry-pick: add t3512 " Jens Lehmann
2014-06-15 17:03 ` [PATCH 12/14] am: add t4255 " Jens Lehmann
2014-06-15 17:04 ` [PATCH 13/14] stash: add t3906 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:04 ` [PATCH 14/14] revert: add t3513 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-07-02 14:54 ` [PATCH 00/14] Add submodule test harness Torsten Bögershausen
2014-07-02 19:57 ` Jens Lehmann
2014-07-03 5:56 ` Torsten Bögershausen
2014-07-03 21:14 ` Jens Lehmann
2014-07-07 17:05 ` Junio C Hamano
2014-07-07 19:40 ` Torsten Bögershausen
2014-07-08 19:34 ` Jens Lehmann
2014-07-08 20:25 ` Ramsay Jones
2014-07-08 21:03 ` Ramsay Jones
2014-07-09 6:39 ` No fchmod() under msygit - Was: " Torsten Bögershausen
2014-07-09 20:00 ` Eric Wong
2014-07-14 11:31 ` Erik Faye-Lund
2014-07-14 13:55 ` Nico Williams
2014-07-14 14:02 ` Nico Williams
2014-07-14 19:30 ` Karsten Blees
2014-07-14 21:18 ` Junio C Hamano
2014-07-09 6:14 ` Torsten Bögershausen
2014-07-09 15:20 ` Junio C Hamano
2014-07-09 18:19 ` Jens Lehmann
2014-07-09 19:31 ` Junio C Hamano
2014-07-10 20:52 ` Junio C Hamano
2014-07-12 18:23 ` Jens Lehmann
2014-07-14 1:01 ` Junio C Hamano
2014-07-14 18:22 ` Jens Lehmann
2014-07-14 21:18 ` Junio C Hamano
2014-07-09 17:21 ` Johannes Sixt
2014-07-09 19:22 ` Junio C Hamano
2014-07-09 19:56 ` Eric Wong
2014-07-09 21:57 ` Junio C Hamano
2014-07-10 6:22 ` No fchmd. was: " Torsten Bögershausen
2014-07-10 19:49 ` Junio C Hamano
2014-07-10 20:55 ` Torsten Bögershausen
2014-07-10 21:43 ` 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=539DD029.4030506@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).