From: newren@gmail.com
To: git@vger.kernel.org
Cc: Johannes.Schindelin@gmx.de, kusmabite@gmail.com
Subject: A few fast export fixups -- round 3
Date: Thu, 25 Jun 2009 22:48:26 -0600 [thread overview]
Message-ID: <1245991713-12782-1-git-send-email-newren@gmail.com> (raw)
This patch series fixes a few fast-export bugs I have come across,
plus some new testcases to verify the fixes, a testcase to document a
pre-existing failure, and finally a small addition to the
documentation.
Changes since v1:
- fixed test issues identified by Johannes Sixt and Stephen Boyd
- squashed patch #2 into patch #1
Changes since v2:
- several changes and improvements suggested by Junio (moving code
to different functions, avoiding exporting functionality from
revision.c, improved commit messages)
- new patch to ensure invariants created by setup_revisions are
respected (set revs flags before calling setup_revisions, rather
than after)
- now also catches and omits tags of tags of trees, tags of tags of
tags of trees, etc.
- remove some now-obsoleted code
- There are two new cases I'm aware of in which fast-export produces
broken "(null)" refs; I'm not sure how/where to fix these (or even
what correct behavior is in one of the cases), but they are no worse
than before and I've at least added a test documenting that we know
that there's a case that is (still) broken.
Elijah Newren (7):
fast-export: Set revs.topo_order before calling setup_revisions
fast-export: Omit tags that tag trees
fast-export: Make sure we show actual ref names instead of "(null)"
fast-export: Do parent rewriting to avoid dropping relevant commits
fast-export: Add a --tag-of-filtered-object option for newly dangling tags
Add new fast-export testcases
fast-export: Document the fact that git-rev-list arguments are accepted
Documentation/git-fast-export.txt | 17 +++++++
builtin-fast-export.c | 82 +++++++++++++++++++++++++++++---
t/t9301-fast-export.sh | 96 ++++++++++++++++++++++++++++++++++++-
3 files changed, 187 insertions(+), 8 deletions(-)
next reply other threads:[~2009-06-26 4:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 4:48 newren [this message]
2009-06-26 4:48 ` [PATCHv3 1/7] fast-export: Set revs.topo_order before calling setup_revisions newren
2009-06-26 4:48 ` [PATCHv3 2/7] fast-export: Omit tags that tag trees newren
2009-06-26 4:48 ` [PATCHv3 3/7] fast-export: Make sure we show actual ref names instead of "(null)" newren
2009-06-26 4:48 ` [PATCHv3 4/7] fast-export: Do parent rewriting to avoid dropping relevant commits newren
2009-06-26 4:48 ` [PATCHv3 5/7] fast-export: Add a --tag-of-filtered-object option for newly dangling tags newren
2009-06-26 4:48 ` [PATCHv3 6/7] Add new fast-export testcases newren
2009-06-26 4:48 ` [PATCHv3 7/7] fast-export: Document the fact that git-rev-list arguments are accepted newren
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=1245991713-12782-1-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
/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).