From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Johan Herland <johan@herland.net>,
David Aguilar <davvid@gmail.com>
Subject: Re: Latest git-remote-cvs?
Date: Sun, 2 May 2010 15:34:39 +0200 [thread overview]
Message-ID: <i2sfabb9a1e1005020634x5d600f95n585f4e4d8a0cfdba@mail.gmail.com> (raw)
In-Reply-To: <20100502101726.GA2514@progeny.tock>
Heya,
On Sun, May 2, 2010 at 12:17, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Occasionally I find a few minutes to dabble with remote-cvs, but now my
> branch is starting to bitrot. The latest iteration of the patches I
> can find is that posted by Sverre on 29 October[1]; has there been any
> progress since then? I am wondering in case time suddenly frees up to
> start rebasing.
Nope, I haven't rebased it since you said to take it out. If you need
help with rebasing it to match the latest protocol etc., feel free to
ping me :).
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2010-05-02 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 10:17 Latest git-remote-cvs? Jonathan Nieder
2010-05-02 13:34 ` Sverre Rabbelier [this message]
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=i2sfabb9a1e1005020634x5d600f95n585f4e4d8a0cfdba@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=jrnieder@gmail.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).