git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 5/5] drop vcs-svn experiment
Date: Thu, 13 Aug 2020 11:18:31 -0400	[thread overview]
Message-ID: <20200813151831.GB892741@coredump.intra.peff.net> (raw)
In-Reply-To: <20200813151136.GC2244@syl.lan>

On Thu, Aug 13, 2020 at 11:11:36AM -0400, Taylor Blau wrote:

> > So it seems like the result is not really usable by anybody in practice.
> > It would be wonderful if somebody wanted to pick up the topic again, and
> > potentially it's worth carrying around for that reason. But the flip
> > side is that people doing tree-wide operations have to deal with this
> > code.  And you can see the list with (replace "HEAD" with this commit as
> > appropriate):
> 
> I have nothing to add to this email other than to say that I think it
> makes sense to remove this. I agree it would be nice if somebody picked
> it up, but given that nothing has really changed since ~8 years ago, I
> think that it's unlikely to happen in the next ~8 years ;).
> 
> At least, it seems unlikely enough that dropping 2MB from the
> installation size is worth it. If someone *is* interested in picking it
> up, I'm sure that they won't have trouble finding this patch and
> reverting it.

TBH I care less about the installation size (which we could easily fix
by just not installing git-remote-testsvn) and more that it's 3000 lines
of basically-dead code. That keeps getting touched for tree-wide
refactors (most recently for strvec, but my -Wunused-parameters series
was the straw that caused me to just delete it instead).

I don't think resurrecting it will be quite as easy as reverting this.
Because the rest of the code will move on, so it will probably need
some fixups, depending on how long it has been. But those fixups are the
exact same changes we're saving regular git developers from doing. So
it's really just gambling that we won't need to do them (and also
shifting the work from everybody onto whoever chooses to work on this).

It would be nice if it could be spun out independently, but it does use
a bunch of data structures from libgit.a, which complicates that.

-Peff

  reply	other threads:[~2020-08-13 15:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 14:55 [PATCH 0/5] slimming down installed size Jeff King
2020-08-13 14:57 ` [PATCH 1/5] Makefile: drop builtins from MSVC pdb list Jeff King
2020-08-13 15:04   ` Taylor Blau
2020-08-13 15:08     ` Jeff King
2020-08-13 16:37       ` Derrick Stolee
2020-08-13 17:40         ` Jeff King
2020-08-14 14:18       ` Johannes Schindelin
2020-08-14 14:32         ` Jeff King
2020-08-17  4:42           ` Johannes Schindelin
2020-08-17 13:20         ` Jeff Hostetler
2020-08-13 14:58 ` [PATCH 2/5] make credential helpers builtins Jeff King
2020-08-13 15:08   ` Taylor Blau
2020-08-13 15:14     ` Jeff King
2020-08-13 17:55       ` Junio C Hamano
2020-08-13 14:59 ` [PATCH 3/5] make git-bugreport a builtin Jeff King
2020-08-13 17:01   ` Derrick Stolee
2020-08-13 17:38     ` Jeff King
2020-08-13 18:25       ` Junio C Hamano
2020-08-13 18:47         ` Junio C Hamano
2020-08-14 10:13           ` Jeff King
2020-08-14 14:25           ` Johannes Schindelin
2020-08-14 10:05         ` Jeff King
2020-08-13 18:01   ` Junio C Hamano
2020-08-14 14:28     ` Johannes Schindelin
2020-08-15  6:38     ` Jeff King
2020-08-17 12:12       ` Emily Shaffer
2020-08-17 16:58       ` Junio C Hamano
2020-08-17 21:40         ` Jeff King
2020-08-17 12:16   ` Emily Shaffer
2020-08-13 14:59 ` [PATCH 4/5] make git-fast-import " Jeff King
2020-08-13 15:00 ` [PATCH 5/5] drop vcs-svn experiment Jeff King
2020-08-13 15:11   ` Taylor Blau
2020-08-13 15:18     ` Jeff King [this message]
2020-08-14 14:39   ` Johannes Schindelin
2020-08-14 15:11     ` Jeff King
2020-08-13 15:13 ` [PATCH 0/5] slimming down installed size Taylor Blau

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=20200813151831.GB892741@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=me@ttaylorr.com \
    --subject='Re: [PATCH 5/5] drop vcs-svn experiment' \
    /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

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).