All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
	Junio C Hamano <gitster@pobox.com>,
	Victoria Dye <vdye@github.com>,
	Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [PATCH] Add ideas for GSoC 2024
Date: Fri, 9 Feb 2024 07:27:43 +0100	[thread overview]
Message-ID: <ZcXF30FFOo5cWeFT@tanuki> (raw)
In-Reply-To: <F2684AB9-C4F3-43C3-91F2-A6D7D71F4927@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

On Thu, Feb 08, 2024 at 07:32:50PM +0530, Kaartic Sivaraam wrote:
> Hi Patrick amd Christian,
> 
> 
> On 6 February 2024 1:43:02 pm IST, Christian Couder <christian.couder@gmail.com> wrote:
> >On Tue, Feb 6, 2024 at 6:51 AM Patrick Steinhardt <ps@pks.im> wrote:
> >> On Tue, Feb 06, 2024 at 12:25:31AM +0530, Kaartic Sivaraam wrote:
> >
> >> I don't quite mind either way. I think overall we have enough tests that
> >> can be converted even if both projects got picked up separately. And the
> >> reftable unit tests are a bit more involved than the other tests given
> >> that their coding style doesn't fit at all into the Git project. So it's
> >> not like they can just be copied over, they definitely need some special
> >> care.
> >>
> >> Also, the technical complexity of the "reftable" backend is rather high,
> >> which is another hurdle to take.
> >>
> >> Which overall makes me lean more towards keeping this as a separate
> >> project now that I think about it.
> 
> Makes sense.  I suppose we need to capture the distinction more
> clearly in the ideas page.
> 
> I've tweaked the doc for the same. Do check it out and feel free to
> suggest any corrections.
> 
> Ideas page: https://git.github.io/SoC-2024-Ideas/

Yeah, the clarification looks good to me. Thanks!

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-09  6:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 18:16 Git in GSoC 2024 Kaartic Sivaraam
2024-01-30  8:38 ` Christian Couder
2024-01-30  9:08   ` Patrick Steinhardt
2024-01-31 13:10     ` Patrick Steinhardt
2024-01-31 17:57       ` Kaartic Sivaraam
2024-01-31 18:03         ` Kaartic Sivaraam
2024-02-01  9:00         ` Karthik Nayak
2024-02-01  9:38         ` Patrick Steinhardt
2024-02-03 11:41           ` Kaartic Sivaraam
2024-02-04 14:29             ` Kaartic Sivaraam
2024-02-05  8:39             ` [PATCH] Add ideas for " Patrick Steinhardt
2024-02-05 16:43               ` Christian Couder
2024-02-05 18:55                 ` Kaartic Sivaraam
2024-02-06  5:51                   ` Patrick Steinhardt
2024-02-06  8:13                     ` Christian Couder
2024-02-08 14:02                       ` Kaartic Sivaraam
2024-02-09  6:27                         ` Patrick Steinhardt [this message]
2024-02-09  8:36                         ` Christian Couder
2024-02-06  5:47                 ` Patrick Steinhardt
2024-02-06  8:26                   ` Christian Couder
2024-02-05 17:07             ` Git in " Christian Couder
2024-02-05 18:39               ` Kaartic Sivaraam
2024-02-21  5:02                 ` Kaartic Sivaraam
2024-02-21  6:19                   ` Patrick Steinhardt
2024-02-21  8:43                   ` Christian Couder
2024-02-21  8:59                   ` Karthik Nayak
2024-02-22  4:31                   ` Kaartic Sivaraam
2024-02-22  7:49                     ` Patrick Steinhardt
2024-02-22  8:57                       ` Karthik Nayak
2024-02-22 12:02                         ` Christian Couder
2024-02-22 14:05                       ` Kaartic Sivaraam
2024-02-22 15:52                         ` Patrick Steinhardt
2024-02-24 17:34                           ` Kaartic Sivaraam

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

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

  git send-email \
    --in-reply-to=ZcXF30FFOo5cWeFT@tanuki \
    --to=ps@pks.im \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=vdye@github.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.