From: Junio C Hamano <email@example.com> To: Johannes Schindelin <Johannes.Schindelin@gmx.de> Cc: Christian Couder <firstname.lastname@example.org>, Shawn Pearce <email@example.com>, Stefan Saasen <firstname.lastname@example.org>, Git Mailing List <email@example.com> Subject: Re: Git clonebundles Date: Tue, 07 Feb 2017 12:54:09 -0800 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <alpine.DEB.2.20.1702071303370.3496@virtualbox> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: >> If people think it might be useful to have it around to experiment, I >> can resurrect and keep that in 'pu' (or rather 'jch'), as long as it >> does not overlap and conflict with other topics in flight. Let me try >> that in today's integration cycle. > > I would like to remind you of my suggestion to make this more publicly > visible and substantially easier to play with, by adding it as an > experimental feature (possibly guarded via an explicit opt-in config > setting). I do not understand why you want to give this topic undue prominence ovver any other random topic that cook in 'pu' and later merged down to 'next' and then 'master' only after they turn out to be useful (or at least harmless). If there were somebody who is the champion of that topic, advocating that any clone-bundle solution must be based on this topic, it would be different. Even though I am not opposed to the topic myself, I am not that somebody. That is why I kept it around to wait to see if somebody finds it potentially useful and then discarded it after seeing no such person stepped up. That champion of the topic would spend the necessaly engineering effort to document it as experimental, to make sure that there is a reasonable upgrade/transition route if the "v3" format turns out to be not very useful, etc. by rerolling the patches or following-up on them to advance it from 'pu' down to 'next' and to 'master' just like any other topic. Judging from the tone of his message (i.e. "unfortunately" in it), Christian may want to be one, or somebody else may want to be one.
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-31 7:00 Stefan Saasen 2017-02-04 17:39 ` Shawn Pearce 2017-02-05 16:37 ` Christian Couder 2017-02-06 22:16 ` Junio C Hamano 2017-02-07 12:04 ` Johannes Schindelin 2017-02-07 15:34 ` Stefan Beller 2017-02-07 20:54 ` Junio C Hamano [this message] 2017-02-08 14:28 ` Johannes Schindelin
Reply instructions: You may reply publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
email@example.com mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox