git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git archive invocation using sha1 to specify commit

From
ZCZdenek Crha <zdenek.crha@gmail.com>
Date
Feb 29, 2012, 07:45 UTC
Message-ID
<CA+OUE96-mLc0RJZz0g0oBWxdZKeCMQ9xJbg6DjCacN119TFY+A@mail.gmail.com>
CC me on answers please, since I'm not subscribed to the list
Hello,

I would like to ask a question about commit restriction added to git archive by commit (ee27ca4a: archive: don't let remote clients get unreachable commits, 2011-11-17) and following efforts to loosen them a bit.

In out company we are using git together with source indexing. We store a git command for retrieval of source code file that was used for building into pdb file(s). Currently, we are using an invocation of git archive with --remote parameter and commit sha1 to export exactly the source code that was used for build.

The above mentioned commit removed possibility to do that. I have read about efforts to loosen the restrictions, but I'm not sure whenever ability to export arbitrary sha1 will be allowed too. Can anybody clarify that for me please?

Regards, Zdenek Crha

Next: Junio C Hamano
Message 1 of 3 in “git archive invocation using sha1 to specify commit”
  1. Zdenek CrhaFeb 29, 2012
  2. Junio C HamanoFeb 29, 2012
  3. Jeff KingFeb 29, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.