From: Jeff King <peff@peff.net>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: Markus Heidelberg <markus.heidelberg@web.de>, git@vger.kernel.org
Subject: Re: [PATCH] contrib/vim: change URL to point to the latest syntax files
Date: Tue, 13 Jan 2009 02:56:07 -0500 [thread overview]
Message-ID: <20090113075607.GA15941@coredump.intra.peff.net> (raw)
In-Reply-To: <8763kjej3p.fsf@iki.fi>
On Tue, Jan 13, 2009 at 09:54:50AM +0200, Teemu Likonen wrote:
> Vim is essentially just a one-man project and the maintainer doesn't use
> version control system. He just piles "diff -c" -type patches on top of
> the previous release and sends them to vim-dev mailing list and to some
> FTP site. Then other people try to maintain VCS repositories based on
> the patches and resources that are available.
>
> Vim's bus factor: 1
Ah. He should use git. ;)
Thanks for the explanation.
-Peff
next prev parent reply other threads:[~2009-01-13 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 2:10 [PATCH] contrib/vim: change URL to point to the latest syntax files Markus Heidelberg
2009-01-13 7:16 ` Jeff King
2009-01-13 7:54 ` Teemu Likonen
2009-01-13 7:56 ` Jeff King [this message]
2009-01-13 8:06 ` Junio C Hamano
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=20090113075607.GA15941@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--cc=tlikonen@iki.fi \
/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).