From: John Keeping <john@keeping.me.uk>
To: git@vger.kernel.org
Cc: Dave Abrahams <dave@boostpro.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
John Keeping <john@keeping.me.uk>
Subject: [PATCH 0/4] fast-import: handle empty paths better
Date: Sun, 23 Jun 2013 15:58:18 +0100 [thread overview]
Message-ID: <cover.1371999369.git.john@keeping.me.uk> (raw)
This series addressed Dave Abraham's recent bug report [1] about using
fast-import's "ls" command with an empty path. I also found a couple of
other places that do not handle the empty path when it can reasonably be
interpreted as meaning the root tree object, which are also fixed here.
[1] http://article.gmane.org/gmane.comp.version-control.git/228586
John Keeping (4):
t9300: document fast-import empty path issues
fast-import: set valid mode on root tree in "ls"
fast-import: allow ls or filecopy of the root tree
fast-import: allow moving the root tree
fast-import.c | 58 ++++++++++++++++++++++++++++----------------
t/t9300-fast-import.sh | 65 ++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 103 insertions(+), 20 deletions(-)
--
1.8.3.1.676.gaae6535
next reply other threads:[~2013-06-23 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 14:58 John Keeping [this message]
2013-06-23 14:58 ` [PATCH 1/4] t9300: document fast-import empty path issues John Keeping
2013-06-23 14:58 ` [PATCH 2/4] fast-import: set valid mode on root tree in "ls" John Keeping
2013-06-23 14:58 ` [PATCH 3/4] fast-import: allow ls or filecopy of the root tree John Keeping
2013-06-23 14:58 ` [PATCH 4/4] fast-import: allow moving " John Keeping
2013-07-01 21:57 ` [PATCH 0/4] fast-import: handle empty paths better 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1371999369.git.john@keeping.me.uk \
--to=john@keeping.me.uk \
--cc=dave@boostpro.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.