From: Charles Bailey <charles@hashpling.org>
To: Alessandro Guido <ag@alessandroguido.name>
Cc: git@vger.kernel.org
Subject: Re: git archive problem with 1.6.0.3 (maybe regression?)
Date: Fri, 31 Oct 2008 22:37:10 +0000 [thread overview]
Message-ID: <490B8896.6040007@hashpling.org> (raw)
In-Reply-To: <200810312213.32224.ag@alessandroguido.name>
Alessandro Guido wrote:
> [please CC: me on replies]
>
> Hi everybody.
>
> With git 1.6.0.3, I get the following error when trying to "git archive" on a
> bare clone of the Linux kernel repo:
>
> ~ $ cd Kernel/
> ~/Kernel $ ls
> branches config description FETCH_HEAD HEAD hooks info logs objects
> packed-refs refs
> ~/Kernel $ git archive 721d5df > /dev/null
> fatal: Not a valid object name
>
> With git 1.6.0.2, on the same tree, it works fine.
http://git.kernel.org/?p=git/git.git;a=commit;h=ddff8563510a2c5c675d488a02e2642306430fc1
next prev parent reply other threads:[~2008-10-31 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 21:13 git archive problem with 1.6.0.3 (maybe regression?) Alessandro Guido
2008-10-31 22:37 ` Charles Bailey [this message]
2008-10-31 22:43 ` Alessandro Guido
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=490B8896.6040007@hashpling.org \
--to=charles@hashpling.org \
--cc=ag@alessandroguido.name \
--cc=git@vger.kernel.org \
/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).