From: Duy Nguyen <pclouds@gmail.com>
To: Brandon Williams <bmwill@google.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] push: add documentation on push v2
Date: Thu, 2 Aug 2018 17:17:53 +0200 [thread overview]
Message-ID: <CACsJy8CO=ZUgKgnmM--BpNFFgvM-dAyckeXKeZXHrtzZcZiC+g@mail.gmail.com> (raw)
In-Reply-To: <20180725174622.GA4850@google.com>
On Wed, Jul 25, 2018 at 7:46 PM Brandon Williams <bmwill@google.com> wrote:
> > Could you send a v2 that covers all the push features in pack version
> > 1? I see some are discussed but it's probably good to summarize in
> > this document too.
>
> I can mention the ones we want to implement, but I expect that a push v2
> would not require that all features in the current push are supported
> out of the box. Some servers may not want to support signed-push, etc.
> Also I don't want to have to implement every single feature that exists
> before getting something merged. This way follow on series can be
> written to implement those as new features to push v2.
I thought I wrote this mail but apparently I did not for some unknown
reason. My concern here is painting ourselves in the corner and having
a rough sketch of how current features will be implemented or replaced
in v2 would help reduce that risk.
--
Duy
prev parent reply other threads:[~2018-08-02 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 21:09 [RFC] push: add documentation on push v2 Brandon Williams
2018-07-17 23:25 ` Stefan Beller
2018-07-18 13:31 ` Derrick Stolee
2018-07-18 16:56 ` Stefan Beller
2018-07-18 17:15 ` Brandon Williams
2018-07-20 13:12 ` Jeff Hostetler
2018-07-24 19:00 ` Brandon Williams
2018-07-18 17:11 ` Brandon Williams
2018-07-18 17:19 ` Duy Nguyen
2018-07-18 17:46 ` Brandon Williams
2018-07-18 17:57 ` Duy Nguyen
2018-07-18 17:08 ` Brandon Williams
2018-07-18 18:07 ` Stefan Beller
2018-07-18 18:17 ` Duy Nguyen
2018-07-18 18:21 ` Brandon Williams
2018-07-24 19:28 ` Brandon Williams
2018-07-25 15:15 ` Duy Nguyen
2018-07-25 17:46 ` Brandon Williams
2018-08-02 15:17 ` Duy Nguyen [this message]
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='CACsJy8CO=ZUgKgnmM--BpNFFgvM-dAyckeXKeZXHrtzZcZiC+g@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=bmwill@google.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.
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).