Open GoogleCodeExporter opened 9 years ago
This would be very handy.
For example I just wanted to compile a kernel and I had to get the whole (huge)
git repository for https://android.googlesource.com/platform/prebuilt when just
a checkout of a specific revision would have been enough.
Original comment by a...@amarulasolutions.com
on 10 Apr 2013 at 10:35
You can get an entire tree at just a specific revision via git with a shallow
clone.
Original comment by dborowitz@google.com
on 10 Apr 2013 at 4:45
for me this is a blocker, as this is a very important requirement in my
environment, both: cgit and gitweb are having the feature
Original comment by psz...@gmail.com
on 10 Jun 2013 at 2:49
This is much easier now that JGit has archive support merged upstream.
Original comment by dborowitz@google.com
on 10 Jun 2013 at 4:29
https://gerrit-review.googlesource.com/47141/ added /+archive/ support. The
details of the archive that produces aren't set in stone yet (e.g., I'd like to
make project-revision.tar.gz prefix pathnames of its entries with
project-revision/).
Original comment by jrnieder
on 1 Oct 2013 at 5:58
As per https://github.com/golang/go/issues/11688
Could someone clarify if this is the right google code issue to request an
improvement to the tarball generation, such that when generating new tarball
from the repository it gets a base directory identifying project and tag or
branch?
Original comment by gago...@gmail.com
on 12 Jul 2015 at 10:21
Also, it would be great if the tarball generation created stable tarballs with
matching hashes. That can be achieved by using the timestamp in the git commit
as the timestamp of the files in the tarball.
Original comment by h...@guardianproject.info
on 26 Jul 2015 at 8:02
Original issue reported on code.google.com by
dborowitz@google.com
on 11 Nov 2012 at 11:21