$ git archive -o latest.zip ae6c3bc47$ ls -lh latest.zip-rw-rw-r-- 1 atsaloli atsaloli 1.1K Feb 21 07:23 latest.zip$
--
You received this message because you are subscribed to the Google Groups "GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/3576cabf-a78e-47bd-ace7-ec1a589fd8db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
What is the command that you are running?
I don't have any trouble with "git archive" but it doesn't try to upload anything:$ git archive -o latest.zip ae6c3bc47$ ls -lh latest.zip-rw-rw-r-- 1 atsaloli atsaloli 1.1K Feb 21 07:23 latest.zip$Best,
On Tue, Feb 21, 2017 at 6:20 AM, Ashwini <ashu.r...@gmail.com> wrote:
HiDoes GitLab support git archive command with SHA id? Instead of refs ?when trying to get the data the error occurs:remote: fatal: no such ref: a2501e8bea4b8fea43f55b780a692809207a0260remote: git upload-archive: archiver died with errorfatal: sent error to the client: git upload-archive: archiver died with errorwhere as the reference exist..!!Please helpRegardsAshwini
--
You received this message because you are subscribed to the Google Groups "GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/3576cabf-a78e-47bd-ace7-ec1a589fd8db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ᐧ
To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/56e0b9a5-93ba-4116-977b-dad0dbcfc2ea%40googlegroups.com.
P.S. This restriction was implemented in 1.7.8.1:
Git v1.7.8.1 Release Notes ========================== Fixes since v1.7.8 ------------------ ...
* "git archive" mistakenly allowed remote clients to ask for commits that are not at the tip of any ref.
...
Got it. Git does this by design -- see the excellent answer at https://bitbucket.org/site/master/issues/9243/git-acrhive-remote-does-not-work which links to the Git source code showing that Git only accepts refs (e.g. HEAD or branchname) here, not SHA1's.ᐧ
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/56e0b9a5-93ba-4116-977b-dad0dbcfc2ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ᐧ
To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/24106cf0-b0c1-4852-bbda-405b6765786a%40googlegroups.com.