list mirror (unofficial, one of many)
 help / color / Atom feed
From: Stefan Beller <>
To: Johannes Schindelin <>
Cc: Junio C Hamano <>,
	Christian Couder <>,
	Shawn Pearce <>,
	Stefan Saasen <>,
	Git Mailing List <>
Subject: Re: Git clonebundles
Date: Tue, 7 Feb 2017 07:34:04 -0800
Message-ID: <> (raw)
In-Reply-To: <alpine.DEB.2.20.1702071303370.3496@virtualbox>

On Tue, Feb 7, 2017 at 4:04 AM, Johannes Schindelin
<> wrote:
> Hi Junio,
> On Mon, 6 Feb 2017, Junio C Hamano wrote:
>> Christian Couder <> writes:
>> > There is also Junio's work on Bundle v3 that was unfortunately
>> > recently discarded.  Look for "jc/bundle" in:
>> >
>> >
>> >
>> > and previous "What's cooking in git.git" emails.
>> 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).
> Ciao,
> Johannes

For making this more publicly visible, I want to look into publishing
the cooking reports on the Maybe we can have a "dev"
section there, that has
* a "getting started" section
  linking to
    How to setup your travis
* "current state of development" section
  e.g. the cooking reports, the
  release calender, description of the workflow
  (which branches do exist and serve which purpose),

Most of the static information is already covered quite
well in Documentation/ so there is definitively overlap,
hence lots of links to the ground truth.

The dynamic information however (release calender,
cooking reports) are not described well enough in
Documentation/ so I think we'd want to focus on these
in that dev section.

  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 [this message]
2017-02-07 20:54         ` Junio C Hamano
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	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:

 note: .onion URLs require Tor:
       or Tor2web:

AGPL code for this site: git clone public-inbox