git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Importing Mozilla CVS into git
Date: Thu, 8 Jun 2006 06:29:20 +1200	[thread overview]
Message-ID: <46a038f90606071129g2af6e5e2m7a4b979371d9e5db@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606070915220.5498@g5.osdl.org>

On 6/8/06, Linus Torvalds <torvalds@osdl.org> wrote:
> My guess is that it's the _mozilla_ documentation people that don't
> necessarily have cygwin and perl, because they don't work with the normal
> build.
>
> Ie there are people who can write user documentation, without them having
> any clue - or caring about - build systems.

Which means that git-cvsserver can probably help them -- I don't think
documentation people (and translators, graphic artists, etc) need all
the git smarts. A simplistic TortoiseCVS + git-cvsserver should fit
their usage...

cheers,


martin

  reply	other threads:[~2006-06-07 18:29 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 22:21 Importing Mozilla CVS into git Jon Smirl
2006-06-01 23:20 ` Keith Packard
2006-06-02  0:55   ` Jon Smirl
2006-06-02  2:07     ` Keith Packard
2006-06-02  2:36       ` Jon Smirl
2006-06-02  2:56         ` Shawn Pearce
2006-06-02  3:39         ` Keith Packard
2006-06-02  3:47           ` Jon Smirl
2006-06-02  3:55             ` Keith Packard
2006-06-02  4:00               ` Jon Smirl
2006-06-02  4:11                 ` Shawn Pearce
2006-06-02  4:39                   ` Pavel Roskin
2006-06-02  4:44                     ` Shawn Pearce
2006-06-02  7:46                       ` Johannes Schindelin
2006-06-02  4:44                     ` Jon Smirl
2006-06-07  9:02                       ` Igor Bukanov
2006-06-07 15:21                         ` Pavel Roskin
2006-06-07 15:30                         ` Jon Smirl
2006-06-07 15:58                           ` Jakub Narebski
2006-06-07 16:17                             ` Linus Torvalds
2006-06-07 18:29                               ` Martin Langhoff [this message]
2006-06-02  4:16                 ` Martin Langhoff
2006-06-03 23:16                   ` Robin Rosenberg (list subscriber)
2006-06-03 23:47                     ` Linus Torvalds
2006-06-04  2:24                       ` Bertrand Jacquin
2006-06-04  7:05                       ` Jakub Narebski
2006-06-04 17:55                         ` Linus Torvalds
2006-06-04 19:44                           ` Robin Rosenberg (list subscriber)
2006-06-04 20:00                             ` Linus Torvalds
2006-06-04 21:25                               ` Robin Rosenberg (list subscriber)
2006-06-04 22:02                                 ` Robin Rosenberg (list subscriber)
2006-06-04 23:19                                 ` Linus Torvalds
2006-06-05  0:10                       ` Yakov Lerner
2006-06-03  0:09               ` Jon Smirl
2006-06-03  4:28     ` Jon Smirl
2006-06-06  5:55       ` Martin Langhoff
2006-06-06 15:13         ` Jon Smirl
2006-06-06 19:57           ` Martin Langhoff
2006-06-07  0:12             ` Keith Packard
2006-06-07  0:40           ` Jon Smirl
2006-06-01 23:48 ` Linus Torvalds
2006-06-02  0:59   ` Jon Smirl
2006-06-02  1:11     ` Linus Torvalds
2006-06-02  6:40       ` Junio C Hamano
2006-06-02 15:53         ` Linus Torvalds
2006-06-02 16:00           ` Junio C Hamano
2006-06-02  4:14 ` Martin Langhoff

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=46a038f90606071129g2af6e5e2m7a4b979371d9e5db@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=torvalds@osdl.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).