From: Jeff King <firstname.lastname@example.org> To: Jonathan Tan <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Git in Outreachy December 2019? Date: Thu, 26 Sep 2019 03:09:01 -0400 [thread overview] Message-ID: <20190926070900.GA20653@sigill.intra.peff.net> (raw) In-Reply-To: <email@example.com> On Tue, Sep 24, 2019 at 10:07:46AM -0700, Jonathan Tan wrote: > > > - In your reply  to the above , you mentioned the possibility of > > > keeping a list of cutoff points. One way of doing this, as I state in > > > , is my original suggestion back in 2017 of one such > > > repository-wide list. If we do this, it would be better for > > > fetch-pack to handle this instead of index-pack, and it seems more > > > efficient to me to have index-pack be able to pass objects to > > > fetch-pack as they are inflated instead of fetch-pack rereading the > > > compressed forms on disk (but again, I haven't verified this). > > > > And this is the flip-side problem: we need to get data back, but we have > > only stdout, which is already in use (so we need some kind of protocol). > > That leads to things like the horrible NUL-byte added by 83558686ce > > (receive-pack: send keepalives during quiet periods, 2016-07-15). > > Sounds good. With this, do you think that there is enough likelihood of > acceptance that we can move ahead with my proposed project? > > Besides discussing the likelihood of patches being accepted/rejected, > should we record the result of discussion somewhere (or, if only the > mentor should give their ideas, for me to write in more detail)? I don't > recall a place in the Outreachy form to write this, so I just mentioned > the benefits in outline, but maybe I can just include it somewhere > anyway. Yeah, I think it's OK to go ahead. I think an intern who is interested in the project would get in touch with you either directly, or via the list. So that gives some opportunity to discuss the ideas with them, and to go into more detail on the proposal in an interactive way (it would also be fine to point at this thread, too, of course). -Peff
prev parent reply other threads:[~2019-09-26 7:09 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-27 5:17 Jeff King 2019-08-31 7:58 ` Christian Couder 2019-08-31 19:44 ` Olga Telezhnaya 2019-09-04 19:41 ` Jeff King 2019-09-05 7:24 ` Christian Couder 2019-09-05 19:39 ` Emily Shaffer 2019-09-06 11:55 ` Carlo Arenas 2019-09-07 6:39 ` Jeff King 2019-09-07 10:13 ` Carlo Arenas 2019-09-07 6:36 ` Jeff King 2019-09-08 14:56 ` Pratyush Yadav 2019-09-09 17:00 ` Jeff King 2019-09-23 18:07 ` SZEDER Gábor 2019-09-26 9:47 ` SZEDER Gábor 2019-09-26 19:32 ` Johannes Schindelin 2019-09-26 21:54 ` SZEDER Gábor 2019-09-26 11:42 ` Johannes Schindelin 2019-09-13 20:03 ` Jonathan Tan 2019-09-13 20:51 ` Jeff King 2019-09-16 18:42 ` Emily Shaffer 2019-09-16 21:33 ` Eric Wong 2019-09-16 21:44 ` SZEDER Gábor 2019-09-16 23:13 ` Jonathan Nieder 2019-09-17 0:59 ` Jeff King 2019-09-17 11:23 ` Johannes Schindelin 2019-09-17 12:02 ` SZEDER Gábor 2019-09-23 12:47 ` Johannes Schindelin 2019-09-23 16:58 ` SZEDER Gábor 2019-09-26 11:04 ` Johannes Schindelin 2019-09-26 13:28 ` SZEDER Gábor 2019-09-26 19:39 ` Johannes Schindelin 2019-09-26 21:44 ` SZEDER Gábor 2019-09-27 22:18 ` Jeff King 2019-10-09 17:25 ` SZEDER Gábor 2019-10-11 6:34 ` Jeff King 2019-09-23 18:19 ` Jeff King 2019-09-24 14:30 ` Johannes Schindelin 2019-09-17 15:10 ` Christian Couder 2019-09-23 12:50 ` Johannes Schindelin 2019-09-23 19:30 ` Jeff King 2019-09-23 18:07 ` Jeff King 2019-09-24 14:25 ` Johannes Schindelin 2019-09-24 15:33 ` Jeff King 2019-09-28 3:56 ` Junio C Hamano 2019-09-24 0:55 ` Eric Wong 2019-09-26 12:45 ` Johannes Schindelin 2019-09-30 8:55 ` Eric Wong 2019-09-28 4:01 ` Junio C Hamano 2019-09-20 17:04 ` Jonathan Tan 2019-09-21 1:47 ` Emily Shaffer 2019-09-23 14:23 ` Christian Couder 2019-09-23 19:40 ` Jeff King 2019-09-23 22:29 ` Philip Oakley 2019-10-22 21:16 ` Emily Shaffer 2019-09-23 11:49 ` Christian Couder 2019-09-23 17:58 ` Jonathan Tan 2019-09-23 19:27 ` Jeff King 2019-09-23 20:48 ` Jonathan Tan 2019-09-23 19:15 ` Jeff King 2019-09-23 20:38 ` Jonathan Tan 2019-09-23 21:28 ` Jeff King 2019-09-24 17:07 ` Jonathan Tan 2019-09-26 7:09 ` Jeff King [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=20190926070900.GA20653@sigill.intra.peff.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Git in Outreachy December 2019?' \ /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
Code repositories for project(s) associated with this 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).