user/sven/git.git/archive.c, branch v1.8.0.2

Reduce translations by using same terminologies

2012-08-22T19:02:28Z

Somewhere in help usage, we use both "message" and "msg", "command" and "cmd", "key id" and "key-id". This patch makes all help text from parseopt use the first form. Clearer and 3 fewer strings for translators. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

i18n: archive: mark parseopt strings for translation

2012-08-20T19:23:15Z

Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

Merge branch 'rs/archive-tree-in-tip-simplify'

2012-05-23T20:35:22Z

By René Scharfe * rs/archive-tree-in-tip-simplify: archive-tar: keep const in checksum calculation archive: simplify refname handling

archive: simplify refname handling

2012-05-18T18:26:10Z

There is no need to build a copy of the relevant part of the string just to make sure we have a NUL-terminated string. We can simply pass the length of the interesting part to dwim_ref() instead. Signed-off-by: Rene Scharfe Signed-off-by: Junio C Hamano

archive: delegate blob reading to backend

2012-05-03T17:22:56Z

archive-tar.c and archive-zip.c now perform conversion check, with help of sha1_file_to_archive() from archive.c This gives backends more freedom in dealing with (streaming) large blobs. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

Merge branch 'jk/maint-upload-archive'

2012-01-13T07:34:17Z

* jk/maint-upload-archive: archive: re-allow HEAD:Documentation on a remote invocation

archive: re-allow HEAD:Documentation on a remote invocation

2012-01-12T03:21:22Z

The tightening done in (ee27ca4a: archive: don't let remote clients get unreachable commits, 2011-11-17) went too far and disallowed HEAD:Documentation as it would try to find "HEAD:Documentation" as a ref. Only DWIM the "HEAD" part to see if it exists as a ref. Once we're sure that we've been given a valid ref, we follow the normal code path. This still disallows attempts to access commits which are not branch tips. Signed-off-by: Carlos Martín Nieto Signed-off-by: Junio C Hamano

Merge branch 'jk/maint-upload-archive'

2011-12-14T06:47:38Z

* jk/maint-upload-archive: archive: don't let remote clients get unreachable commits

Merge branch 'jk/maint-1.6.2-upload-archive' into jk/maint-upload-archive

2011-11-21T23:04:11Z

* jk/maint-1.6.2-upload-archive: archive: don't let remote clients get unreachable commits Conflicts: archive.c archive.h builtin-archive.c builtin/upload-archive.c t/t5000-tar-tree.sh

archive: don't let remote clients get unreachable commits

2011-11-21T22:42:25Z

Usually git is careful not to allow clients to fetch arbitrary objects from the database; for example, objects received via upload-pack must be reachable from a ref. Upload-archive breaks this by feeding the client's tree-ish directly to get_sha1, which will accept arbitrary hex sha1s, reflogs, etc. This is not a problem if all of your objects are publicly reachable anyway (or at least public to anybody who can run upload-archive). Or if you are making the repo available by dumb protocols like http or rsync (in which case the client can read your whole object db directly). But for sites which allow access only through smart protocols, clients may be able to fetch trees from commits that exist in the server's object database but are not referenced (e.g., because history was rewound). This patch tightens upload-archive's lookup to use dwim_ref rather than get_sha1. This means a remote client can only fetch the tip of a named ref, not an arbitrary sha1 or reflog entry. This also restricts some legitimate requests, too: 1. Reachable non-tip commits, like: git archive --remote=$url v1.0~5 2. Sub-trees of reachable commits, like: git archive --remote=$url v1.7.7:Documentation Local requests continue to use get_sha1, and are not restricted at all. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano