git-fast-import is not writing a commit even after a checkpoint/progress
command.
See my previous message git p4 diff-tree ambiguous argument error.
The error in git-p4 is caused by git not writing the commit even after
git-fast-import has been given a checkpoint and progress command.
On
On Sat, Jun 22, 2013 at 07:16:48PM -0700, Dave Abrahams wrote:
on Sat Jun 22 2013, John Keeping john-AT-keeping.me.uk wrote:
On Fri, Jun 21, 2013 at 02:21:47AM -0700, Dave Abrahams wrote:
The docs for fast-import seem to imply that I can use ls to get the
SHA1 of a commit for which I
on Sun Jun 23 2013, John Keeping john-AT-keeping.me.uk wrote:
On Sat, Jun 22, 2013 at 07:16:48PM -0700, Dave Abrahams wrote:
I also note that the docs
don't make it clear that quoting the path is mandatory if it might turn
out to be empty.
On Sun, Jun 23, 2013 at 07:19:25AM -0700, Dave Abrahams wrote:
on Sun Jun 23 2013, John Keeping john-AT-keeping.me.uk wrote:
In this case, I think I do now understand why the mode is 0: in
parse_ls a new tree object is created and the SHA1 of the original is
copied in but the mode is left
On Fri, Jun 21, 2013 at 02:21:47AM -0700, Dave Abrahams wrote:
The docs for fast-import seem to imply that I can use ls to get the
SHA1 of a commit for which I have a mark:
Reading from a named tree
The dataref can be a mark reference (:idnum) or the full
40-byte
on Sat Jun 22 2013, John Keeping john-AT-keeping.me.uk wrote:
On Fri, Jun 21, 2013 at 02:21:47AM -0700, Dave Abrahams wrote:
The docs for fast-import seem to imply that I can use ls to get the
SHA1 of a commit for which I have a mark:
Reading from a named tree
The
The docs for fast-import seem to imply that I can use ls to get the
SHA1 of a commit for which I have a mark:
Reading from a named tree
The dataref can be a mark reference (:idnum) or the full 40-byte
SHA-1 of a Git tag, commit, or tree object, preexisting or waiting
7 matches
Mail list logo
