From: Elijah Newren <newren@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Contributor Summit Topics and Logistics
Date: Tue, 22 Jan 2019 12:30:17 -0800 [thread overview]
Message-ID: <CABPp-BE9vTw8vsn=c=wNoTyU6Sg_n4YGEXnGGcFDHRt9Uo5mOg@mail.gmail.com> (raw)
In-Reply-To: <20190122075027.GA29441@sigill.intra.peff.net>
On Mon, Jan 21, 2019 at 11:52 PM Jeff King <peff@peff.net> wrote:
>
> The Git Merge Contributor Summit is a little over a week away. If you're
> interested in coming but haven't signed up, please do! We have a few
> spaces available still. Details are in the previous announcement:
>
> http://public-inbox.org/git/20181206094805.GA1398@sigill.intra.peff.net/
>
> There's no set agenda; we'll decide what to discuss that day. But if
> anybody would like to mention topics they are interested in (whether you
> want to present on them, or just have an open discussion), please do so
> here. A little advance notice can help people prepare more for the
> discussions.
* git repo-filter[1] or whatever it ends up being named (filter-branch
alternative): is it wanted in git.git?
* merge-recursive rewrite -- steps others want to see me take in that process?
* Making --merge option of rebase be the default[2]: what steps need
to be taken?
* I'll second Derrick's request for partial clone, perhaps also
briefly discuss related capabilities like sparse checkouts and partial
indexes too?
[1] https://public-inbox.org/git/20181111062312.16342-1-newren@gmail.com/
[2] https://public-inbox.org/git/xmqqh8jeh1id.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2019-01-22 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 7:50 Contributor Summit Topics and Logistics Jeff King
2019-01-22 8:26 ` Jeff King
2019-01-22 9:17 ` GSoC 2019 (was: Contributor Summit Topics and Logistics) Christian Couder
2019-01-31 2:02 ` SZEDER Gábor
2019-01-31 6:11 ` Christian Couder
2019-01-22 18:21 ` Contributor Summit Topics and Logistics Stefan Beller
2019-01-22 20:53 ` Jeff King
2019-01-22 18:23 ` Derrick Stolee
2019-01-24 8:57 ` Ævar Arnfjörð Bjarmason
2019-01-29 18:22 ` Derrick Stolee
2019-01-22 20:30 ` Elijah Newren [this message]
2019-01-30 20:57 ` Ævar Arnfjörð Bjarmason
2019-01-30 22:26 ` Jeff Hostetler
2019-01-30 22:51 ` Philip Oakley
2019-01-30 23:13 ` Christian Couder
2019-01-30 23:07 ` Jeff King
2019-02-02 12:33 ` Jakub Narebski
2019-02-04 19:30 ` Elijah Newren
2019-04-23 3:45 ` Jeff King
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='CABPp-BE9vTw8vsn=c=wNoTyU6Sg_n4YGEXnGGcFDHRt9Uo5mOg@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--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).