From: Dave Abrahams <dave@boostpro•com>
To: git@vger•kernel.org
Subject: fast-import bug?
Date: Fri, 21 Jun 2013 02:21:47 -0700 [thread overview]
Message-ID: <m2zjuj2504.fsf@cube.gateway.2wire.net> (raw)
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 to
be written. The path is relative to the top level of the tree named by
<dataref>.
'ls' SP <dataref> SP <path> LF
See filemodify above for a detailed description of <path>.
Output uses the same format as git ls-tree <tree> -- <path>:
<mode> SP ('blob' | 'tree' | 'commit') SP <dataref> HT <path> LF
The <dataref> represents the blob, tree, or commit object at <path> and
^^^^^^
can be used in later cat-blob, filemodify, or ls commands.
but I can't get it to work. It's not entirely clear it's supposed to
work. What path would I pass? Passing an empty path simply causes git
to report "missing ".
TIA,
Dave
--
Dave Abrahams
next reply other threads:[~2013-06-21 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 9:21 Dave Abrahams [this message]
2013-06-22 10:21 ` fast-import bug? John Keeping
2013-06-23 2:16 ` Dave Abrahams
2013-06-23 11:09 ` John Keeping
2013-06-23 14:19 ` Dave Abrahams
2013-06-23 14:55 ` John Keeping
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=m2zjuj2504.fsf@cube.gateway.2wire.net \
--to=dave@boostpro$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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