From: Josh Triplett <josh@joshtriplett.org>
To: Jeff King <peff@peff.net>, Jacob Keller <jacob.keller@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: Regarding "git log" on "git series" metadata
Date: Fri, 04 Nov 2016 21:55:23 -0600 [thread overview]
Message-ID: <A269CCA2-5F8C-4AF0-820E-2EA26FEF03D5@joshtriplett.org> (raw)
In-Reply-To: <20161105014817.vm4ush2wfbblzsc7@sigill.intra.peff.net>
On November 4, 2016 7:48:17 PM MDT, Jeff King <peff@peff.net> wrote:
>On Fri, Nov 04, 2016 at 04:34:34PM -0700, Jacob Keller wrote:
>
>> > You might also want fallback rules for storing gitrefs on "old"
>servers
>> > (e.g., backfilling gitrefs you need if the server didn't them in
>the
>> > initial fetch). But I guess storing any gitrefs on such a server is
>> > inherently dangerous, because the server might prune them at any
>time.
>>
>> Is it possible currently for a protocol extension to result in "oh
>the
>> server doesn't support this so I'm going to stop pushing"?
>
>Yes, it would be easy for the client to abort if the server fails to
>advertise a particular extension.
And the reverse (old client, new server) should work as well?
- Josh Triplett
next prev parent reply other threads:[~2016-11-05 3:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:57 Regarding "git log" on "git series" metadata Junio C Hamano
2016-11-04 19:19 ` Jacob Keller
2016-11-04 19:49 ` Jeff King
2016-11-04 21:55 ` Josh Triplett
2016-11-04 23:37 ` Jacob Keller
2016-11-04 23:46 ` Josh Triplett
2016-11-04 23:34 ` Jacob Keller
2016-11-05 1:48 ` Jeff King
2016-11-05 3:55 ` Josh Triplett [this message]
2016-11-05 4:41 ` Jeff King
2016-11-05 4:41 ` Junio C Hamano
2016-11-05 4:44 ` Jeff King
2016-11-05 5:00 ` Junio C Hamano
2016-11-04 20:47 ` Christian Couder
2016-11-04 21:19 ` Josh Triplett
2016-11-04 23:04 ` Christian Couder
2016-11-13 17:50 ` Stefano Zacchiroli
2016-11-05 21:56 ` Christian Couder
2016-11-05 4:42 ` Junio C Hamano
2016-11-05 12:17 ` Christian Couder
2016-11-05 12:45 ` Christian Couder
2016-11-05 15:18 ` Josh Triplett
2016-11-05 20:21 ` Christian Couder
2016-11-05 20:25 ` Josh Triplett
2016-11-06 4:50 ` Jacob Keller
2016-11-06 16:34 ` Josh Triplett
2016-11-06 17:14 ` Junio C Hamano
2016-11-06 17:33 ` Josh Triplett
2016-11-06 20:17 ` Jacob Keller
2016-11-07 1:18 ` Josh Triplett
2016-11-07 5:35 ` Jacob Keller
2016-11-07 9:42 ` Duy Nguyen
2016-11-07 16:11 ` Josh Triplett
2016-11-09 22:57 ` Junio C Hamano
2016-11-04 21:06 ` Josh Triplett
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A269CCA2-5F8C-4AF0-820E-2EA26FEF03D5@joshtriplett.org \
--to=josh@joshtriplett.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).