From: Patrick Steinhardt <ps@pks.im>
To: eugenio gigante <giganteeugenio2@gmail.com>
Cc: git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
kaartic.sivaraam@gmail.com
Subject: Re: [RFC][GSoC] Proposal: Refactor git-bisect(1)
Date: Mon, 25 Mar 2024 12:24:59 +0100 [thread overview]
Message-ID: <ZgFfCxkHzTHoRgmX@tanuki> (raw)
In-Reply-To: <CAFJh0PTxhDSW1qsnVRrDxmMnp5k16nPGe6RAgrmWow0rgYV+dw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Mon, Mar 25, 2024 at 12:00:58PM +0100, eugenio gigante wrote:
> > To further stress the point: the biggest challenge of this project is
> > indeed to find an agreement with the community whether this refactoring
> > will ultimately be worth it. This will require some good arguing on your
> > part why exactly you think this is fine and how exactly this will
> > interact with other implementations of Git like libgit2/JGit/Dulwich. It
> > may very well happen that ultimately the community decides that this
> > whole endeavour is not worth it.
>
> Yeah, I'll try to expand a bit in this direction. Meanwhile, if you think
> there are others tools to look into, besides the already cited
> (libgit2/JGit/Dulwich),
> like UI interfaces or something else, please let me know.
> (Maybe GitLab is something to keep in mind?)
I don't think any of the hosting providers would care. GitLab definitely
does not.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-25 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 10:26 [RFC][GSoC] Proposal: Refactor git-bisect(1) eugenio gigante
2024-03-25 8:27 ` Patrick Steinhardt
2024-03-25 11:00 ` eugenio gigante
2024-03-25 11:24 ` Patrick Steinhardt [this message]
2024-03-28 3:23 ` Kaartic Sivaraam
2024-03-29 9:05 ` eugenio gigante
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=ZgFfCxkHzTHoRgmX@tanuki \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=giganteeugenio2@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.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 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 NNTP newsgroup(s).