git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, srabbelier@gmail.com
Subject: [PATCHv2 0/2] non-incremental mode for fast-export
Date: Sat, 17 Jul 2010 11:00:49 -0600	[thread overview]
Message-ID: <1279386051-31112-1-git-send-email-newren@gmail.com> (raw)

This patch series fixes silently dropped files in uses of fast-export
involving both --import-marks and limiting files by path.  It also
adds a new feature: a --full-tree option to switch from incremental to
comprehensive handling of files in commits.  The two changes are
related in that the bugfix consists of simply automatically activating
the new feature in a case where it is required for correct operation.

There is just one change since the last submission
  * modify one of the new testcases to not depend on the full exact
    output of fast-export (since it is no longer the same in next)
This change enables the series to apply cleanly to next.  All tests
pass with this series applied to either maint or next now.

I'll again note that it may make sense to split this patch series
since the first is a bugfix and thus makes sense to apply to maint,
while the second (whose testcase was the fragile one) is a feature
addition, though a fairly trivial one.

Elijah Newren (2):
      fast-export: Fix dropping of files with --import-marks and path limiting
      fast-export: Add a --full-tree option

 Documentation/git-fast-export.txt |    6 ++++++
 builtin/fast-export.c             |   11 ++++++++++-
 t/t9350-fast-export.sh            |   14 ++++++++++++++
 3 files changed, 30 insertions(+), 1 deletions(-)

             reply	other threads:[~2010-07-17 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17 17:00 Elijah Newren [this message]
2010-07-17 17:00 ` [PATCHv2 1/2] fast-export: Fix dropping of files with --import-marks and path limiting Elijah Newren
2010-07-17 17:00   ` [PATCHv2 2/2] fast-export: Add a --full-tree option Elijah 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1279386051-31112-1-git-send-email-newren@gmail.com \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=srabbelier@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.
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).