Skip to content

G
git

李少辉-开发者 / git
与 Fork 源项目一致

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 24 8月, 2011 4 次提交
  3. 23 8月, 2011 2 次提交
  5. 19 8月, 2011 1 次提交
  7. 18 8月, 2011 1 次提交
  9. 17 8月, 2011 23 次提交
  11. 09 8月, 2011 5 次提交
    • J
      helping smart-http/stateless-rpc fetch race · 051e4005
      由 Junio C Hamano 提交于 
      A request to fetch from a client over smart HTTP protocol is served in
multiple steps. In the first round, the server side shows the set of refs
it has and their values, and the client picks from them and sends "I want
to fetch the history leading to these commits".

When the server tries to respond to this second request, its refs may have
progressed by a push from elsewhere. By design, we do not allow fetching
objects that are not at the tip of an advertised ref, and the server
rejects such a request. The client needs to try again, which is not ideal
especially for a busy server.

Teach upload-pack (which is the workhorse driven by git-daemon and smart
http server interface) that it is OK for a smart-http client to ask for
commits that are not at the tip of any advertised ref, as long as they are
reachable from advertised refs.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      051e4005
    • J
      receive-pack: do not overstep command line argument array · 0d086b8e
      由 Junio C Hamano 提交于 
      Previous commit added one element to the command line, without
making sure the result fits there.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      0d086b8e
    • M
      filter-branch: Export variable `workdir' for --commit-filter · 0906f6e1
      由 Michael Witten 提交于 
      According to `git help filter-branch':

       --commit-filter <command>
           ...
           You can use the _map_ convenience function in this filter,
           and other convenience functions, too...
           ...

However, it turns out that `map' hasn't been usable because it depends
on the variable `workdir', which is not propogated to the environment
of the shell that runs the commit-filter <command> because the
shell is created via a simple-command rather than a compound-command
subshell:

 @SHELL_PATH@ -c "$filter_commit" "git commit-tree" \
                 $(git write-tree) $parentstr < ../message > ../map/$commit ||
                         die "could not write rewritten commit"

One solution is simply to export `workdir'. However, it seems rather
heavy-handed to export `workdir' to the environments of all commands,
so instead this commit exports `workdir' for only the duration of the
shell command in question:

 workdir=$workdir @SHELL_PATH@ -c "$filter_commit" "git commit-tree" \
                 $(git write-tree) $parentstr < ../message > ../map/$commit ||
                         die "could not write rewritten commit"
Signed-off-by: NMichael Witten <mfwitten@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      0906f6e1
    • E
      Documentation/Makefile: add *.pdf to `clean' target · ae8044a2
      由 Emilio G. Cota 提交于 
      user-manual.pdf is not removed by `make clean'; fix it.
Signed-off-by: NEmilio G. Cota <cota@braap.org>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      ae8044a2
    • E
      Documentation: ignore *.pdf files · 070648e9
      由 Emilio G. Cota 提交于 
      user-manual.pdf is generated by the build and therefore
should be ignored by git.
Signed-off-by: NEmilio G. Cota <cota@braap.org>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      070648e9
  13. 06 8月, 2011 1 次提交
    • J
      fast-export: quote paths in output · 6280dfdc
      由 Jeff King 提交于 
      Many pathnames in a fast-import stream need to be quoted. In
particular:

  1. Pathnames at the end of an "M" or "D" line need quoting
     if they contain a LF or start with double-quote.

  2. Pathnames on a "C" or "R" line need quoting as above,
     but also if they contain spaces.

For (1), we weren't quoting at all. For (2), we put
double-quotes around the paths to handle spaces, but ignored
the possibility that they would need further quoting.

This patch checks whether each pathname needs c-style
quoting, and uses it. This is slightly overkill for (1),
which doesn't actually need to quote many characters that
vanilla c-style quoting does. However, it shouldn't hurt, as
any implementation needs to be ready to handle quoted
strings anyway.

In addition to adding a test, we have to tweak a test which
blindly assumed that case (2) would always use
double-quotes, whether it needed to or not.
Signed-off-by: NJeff King <peff@peff.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      6280dfdc
  15. 04 8月, 2011 3 次提交