From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Scott Chacon <schacon@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: [PATCH] Update packfile transfer protocol documentation
Date: Mon, 2 Nov 2009 16:58:15 -0800 [thread overview]
Message-ID: <20091103005815.GW10505@spearce.org> (raw)
In-Reply-To: <7vtyxctpf8.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> > Junio C Hamano <gitster@pobox.com> wrote:
> > ...
> >> Shouldn't we say "the client MUST NOT make reference update request if
> >> everything is up to date" which would imply that in practice there is no
> >> reason to send an empty pack data?
Creating new branch quirk aside, I do agree with this. Clients
shouldn't send no-op updates if it knows in advance the update is
a no-op.
--
Shawn.
next prev parent reply other threads:[~2009-11-03 0:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 23:18 [PATCH] Update packfile transfer protocol documentation Scott Chacon
2009-11-02 5:17 ` Junio C Hamano
2009-11-02 15:41 ` Shawn O. Pearce
2009-11-02 17:31 ` Junio C Hamano
2009-11-02 15:43 ` Shawn O. Pearce
2009-11-02 23:48 ` Junio C Hamano
2009-11-02 23:57 ` Shawn O. Pearce
2009-11-03 0:36 ` Junio C Hamano
2009-11-03 0:58 ` Shawn O. Pearce [this message]
2009-11-03 22:05 ` Scott Chacon
2009-11-04 0:40 ` Junio C Hamano
2009-11-04 0:40 ` Junio C Hamano
2009-11-04 0:56 ` Shawn O. Pearce
2009-11-04 1:07 ` Junio C Hamano
2009-11-04 1:18 ` Shawn O. Pearce
2009-11-04 1:48 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2009-11-04 5:58 Scott Chacon
2009-11-04 6:36 ` Sverre Rabbelier
2009-11-05 5:24 ` Junio C Hamano
2009-10-29 17:35 Scott Chacon
2009-10-30 22:07 ` Junio C Hamano
2009-10-31 2:06 ` Shawn O. Pearce
2009-10-31 20:12 ` Johannes Sixt
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=20091103005815.GW10505@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schacon@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.