From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Cc: git@tpope.info
Subject: Re: git filetypes for vim
Date: Wed, 3 Oct 2007 18:03:12 +0100 [thread overview]
Message-ID: <20071003170312.GA15632@lapse.madduck.net> (raw)
In-Reply-To: <20071003160745.GA8173@lapse.madduck.net>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
also sprach martin f krafft <madduck@madduck.net> [2007.10.03.1707 +0100]:
> My repo is here: http://git.madduck.net/v/misc/vim-git.git
> Tim's is here: git://git.tpope.net/~tpope/vim-git.git
We had to rewrite the repos history because some information slipped
in that we didn't want archived forever. I am sorry about this.
Please reclone.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
kermit: why are there so many songs about rainbows?
fozzy: that's part of what rainbows do.
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2007-10-03 17:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20071003160745.GA8173@lapse.madduck.net>]
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=20071003170312.GA15632@lapse.madduck.net \
--to=madduck@madduck.net \
--cc=git@tpope.info \
--cc=git@vger.kernel.org \
/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).