git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Todd Zullinger <tmz@pobox.com>, Git Mailing list <git@vger.kernel.org>
Subject: Re: categorization, documentation and packaging of "git core" commands
Date: Wed, 7 Feb 2018 15:14:17 -0500	[thread overview]
Message-ID: <20180207201417.GB9141@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.21.1802071500220.14248@localhost.localdomain>

On Wed, Feb 07, 2018 at 03:03:31PM -0500, Robert P. J. Day wrote:

>   huh ... well, that raises the question, if tla has been unbuildable
> for that long (possibly for other distros), what is the value in
> continuing to support git-archimport?
> 
>   https://www.kernel.org/pub/software/scm/git/docs/git-archimport.html

I don't think that we do really support archimport. It's just that we
tend to leave things sitting around if they're not actively causing us
work, in the off chance that somebody might find them useful.

I'd be OK with declaring archimport dead and unmaintained, and dropping
it totally (I almost did so a few months ago when it _did_ cause me
extra work, because it contained a bunch of shell injections that I
turned up while auditing the whole code base).

-Peff

  reply	other threads:[~2018-02-07 20:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 13:18 categorization, documentation and packaging of "git core" commands Robert P. J. Day
2018-02-07 17:29 ` Todd Zullinger
2018-02-07 18:09   ` Robert P. J. Day
2018-02-07 18:42     ` Todd Zullinger
2018-02-07 20:03   ` Robert P. J. Day
2018-02-07 20:14     ` Jeff King [this message]
2018-02-07 20:38   ` Robert P. J. Day
2018-02-07 21:18     ` Todd Zullinger
2018-02-09 13:51       ` Robert P. J. Day

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=20180207201417.GB9141@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    --cc=tmz@pobox.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).