summaryrefslogtreecommitdiff
path: root/builtin/show-ref.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-07-09 18:01:06 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-07-23 05:18:19 (GMT)
commit91048a9537a4716c84934e4f8ed114a20606d3ff (patch)
tree7421ff6ea3478b843f112a4abf0d8674dbe5a5b3 /builtin/show-ref.c
parent28f5d176110d2ed768a0a49159993c7a02d8cb15 (diff)
downloadgit-91048a9537a4716c84934e4f8ed114a20606d3ff.zip
git-91048a9537a4716c84934e4f8ed114a20606d3ff.tar.gz
git-91048a9537a4716c84934e4f8ed114a20606d3ff.tar.bz2
push --force-with-lease: implement logic to populate old_sha1_expect[]
This plugs the push_cas_option data collected by the command line option parser to the transport system with a new function apply_push_cas(), which is called after match_push_refs() has already been called. At this point, we know which remote we are talking to, and what remote refs we are going to update, so we can fill in the details that may have been missing from the command line, such as (1) what abbreviated refname the user gave us matches the actual refname at the remote; and (2) which remote-tracking branch in our local repository to read the value of the object to expect at the remote. to populate the old_sha1_expect[] field of each of the remote ref. As stated in the documentation, the use of remote-tracking branch as the default is a tentative one, and we may come up with a better logic as we gain experience. Still nobody uses this information, which is the topic of the next patch. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/show-ref.c')
0 files changed, 0 insertions, 0 deletions