From: Jonathan Nieder <jrnieder@gmail.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: http-protocol question
Date: Mon, 1 Dec 2014 19:34:16 -0800 [thread overview]
Message-ID: <20141202033416.GY6527@google.com> (raw)
In-Reply-To: <CAGyf7-HmvvHQZkyLgKAs2rrZTTLFkBa8s828hbS9LedLNb2fWA@mail.gmail.com>
Hi Bryan,
Bryan Turner wrote:
> Is there actually logic somewhere in Git that does that "MAY walk
> backwards" step?
Yes. See upload-pack.c::check_non_tip and
http://thread.gmane.org/gmane.comp.version-control.git/178814.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2014-12-02 3:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 2:17 http-protocol question Bryan Turner
2014-12-02 3:34 ` Jonathan Nieder [this message]
2014-12-02 4:28 ` Bryan Turner
2014-12-02 4:29 ` Bryan Turner
2014-12-02 4:45 ` Jonathan Nieder
2014-12-02 5:04 ` Bryan Turner
2014-12-02 5:17 ` Jonathan Nieder
2014-12-02 5:30 ` Duy Nguyen
2014-12-02 5:37 ` Duy Nguyen
2014-12-02 5:33 ` Jeff King
2014-12-02 5:47 ` Bryan Turner
2014-12-02 5:52 ` Jeff King
2014-12-02 17:45 ` Junio C Hamano
2014-12-02 19:50 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141202033416.GY6527@google.com \
--to=jrnieder@gmail.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).