Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: git/git
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 30b015bffe
Choose a base ref
...
head repository: git/git
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 5e3548ef16
Choose a head ref
  • 4 commits
  • 46 files changed
  • 2 contributors

Commits on Apr 24, 2018

  1. Merge branch 'bw/protocol-v2' into HEAD 

    * bw/protocol-v2: (35 commits)
  remote-curl: don't request v2 when pushing
  remote-curl: implement stateless-connect command
  http: eliminate "# service" line when using protocol v2
  http: don't always add Git-Protocol header
  http: allow providing extra headers for http requests
  remote-curl: store the protocol version the server responded with
  remote-curl: create copy of the service name
  pkt-line: add packet_buf_write_len function
  transport-helper: introduce stateless-connect
  transport-helper: refactor process_connect_service
  transport-helper: remove name parameter
  connect: don't request v2 when pushing
  connect: refactor git_connect to only get the protocol version once
  fetch-pack: support shallow requests
  fetch-pack: perform a fetch using v2
  upload-pack: introduce fetch server command
  push: pass ref prefixes when pushing
  fetch: pass ref prefixes when fetching
  ls-remote: pass ref prefixes when requesting a remote's refs
  transport: convert transport_get_remote_refs to take a list of ref prefixes
  ...
    @gitster
    gitster committed Apr 24, 2018
    Configuration menu
    Copy the full SHA
    bbc39d4 View commit details
    Browse the repository at this point in the history

  2. serve: introduce the server-option capability 

    Introduce the "server-option" capability to protocol version 2.  This
enables future clients the ability to send server specific options in
command requests when using protocol version 2.

Signed-off-by: Brandon Williams <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
    @bmwill @gitster
    bmwill authored and gitster committed Apr 24, 2018
    Configuration menu
    Copy the full SHA
    ecc3e53 View commit details
    Browse the repository at this point in the history

  3. ls-remote: send server options when using protocol v2 

    Teach ls-remote to optionally accept server options by specifying them
on the cmdline via '-o' or '--server-option'.  These server options are
sent to the remote end when querying for the remote end's refs using
protocol version 2.

If communicating using a protocol other than v2 the provided options are
ignored and not sent to the remote end.

Signed-off-by: Brandon Williams <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
    @bmwill @gitster
    bmwill authored and gitster committed Apr 24, 2018
    Configuration menu
    Copy the full SHA
    ff47322 View commit details
    Browse the repository at this point in the history

  4. fetch: send server options when using protocol v2 

    Teach fetch to optionally accept server options by specifying them on
the cmdline via '-o' or '--server-option'.  These server options are
sent to the remote end when performing a fetch communicating using
protocol version 2.

If communicating using a protocol other than v2 the provided options are
ignored and not sent to the remote end.

Signed-off-by: Brandon Williams <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
    @bmwill @gitster
    bmwill authored and gitster committed Apr 24, 2018
    Configuration menu
    Copy the full SHA
    5e3548e View commit details
    Browse the repository at this point in the history
Loading