From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
Sergei Organov <osv@javad.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2] cvsserver: make the output of 'update' more compatible with cvs.
Date: Thu, 31 Dec 2009 16:20:26 +0100 [thread overview]
Message-ID: <46a038f90912310720l4b1cbdebs2b85774ae7e33c0e@mail.gmail.com> (raw)
In-Reply-To: <7vfx6rzlkg.fsf@alter.siamese.dyndns.org>
On Thu, Dec 31, 2009 at 7:47 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Well, since I don't use cvsserver myself, but this v2 was done with
> improvements based on some review suggestions, I was waiting for a
> response or two from people who know better and care more about cvs server
> emulation than me, which unfortunately didn't happen.
Looks good to me -- good to get it into pu. While I continue to use
git extensively, I don't use cvsserver anymore, nor work with people
that do. Might have reason to revisit cvsserver in the near future
though, to help Moodle transition to git.
That transition will bring a few top-posters and Eclipse lovers to the
list. Looking past such details, they are fine people who may need a
little bit of git-newbie help ;-)
happy new year,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-12-31 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 20:12 [PATCH] cvsserver: make the output of 'update' more compatible with cvs Sergei Organov
2009-12-05 23:48 ` mmogilvi_git
2009-12-07 8:27 ` Sergei Organov
2009-12-07 11:11 ` [PATCH v2] " Sergei Organov
2009-12-30 13:41 ` Nanako Shiraishi
2009-12-31 6:47 ` Junio C Hamano
2009-12-31 15:20 ` Martin Langhoff [this message]
2009-12-31 20:14 ` 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=46a038f90912310720l4b1cbdebs2b85774ae7e33c0e@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@lavabit.com \
--cc=osv@javad.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).