From: Taylor Blau <email@example.com> To: Jeff King <firstname.lastname@example.org> Cc: email@example.com, Jonathan Nieder <firstname.lastname@example.org> Subject: Re: [PATCH 5/5] drop vcs-svn experiment Date: Thu, 13 Aug 2020 11:11:36 -0400 [thread overview] Message-ID: <20200813151136.GC2244@syl.lan> (raw) In-Reply-To: <20200813150017.GE891370@coredump.intra.peff.net> On Thu, Aug 13, 2020 at 11:00:17AM -0400, Jeff King wrote: > The code in vcs-svn was started in 2010 as an attempt to build a > remote-helper for interacting with svn repositories (as opposed to > git-svn). However, we never got as far as shipping a mature remote > helper, and the last substantive commit was e99d012a6bc in 2012. > > We do have a git-remote-testsvn, and it is even installed as part of > "make install". But given the name, it seems unlikely to be used by > anybody (you'd have to explicitly "git clone testsvn::$url", and there > have been zero mentions of that on the mailing list since 2013, and even > that includes the phrase "you might need to hack a bit to get it working > properly"). > > We also ship contrib/svn-fe, which builds on the vcs-svn work. However, > it does not seem to build out of the box for me, as the link step misses > some required libraries for using libgit.a. Curiously, the original > build breakage bisects for me to eff80a9fd9 (Allow custom "comment > char", 2013-01-16), which seems unrelated. There was an attempt to fix > it in da011cb0e7 (contrib/svn-fe: fix Makefile, 2014-08-28), but on my > system that only switches the error message. > > 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. Thanks. > [snip] Thanks, Taylor
next prev parent reply other threads:[~2020-08-13 15:11 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 [this message] 2020-08-13 15:18 ` Jeff King 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 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=20200813151136.GC2244@syl.lan \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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
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).