git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: fromcvs installation [was: cvsimport bug on branches [was: conversion to git]]
Date: Sat, 22 Sep 2007 17:08:59 +0200	[thread overview]
Message-ID: <46F5300B.2000707@fs.ei.tum.de> (raw)
In-Reply-To: <86B33DFE-65E6-4F8D-8483-509ACA4FA2F8@zib.de>

Steffen Prohaska wrote:
> Nonetheless a more detailed description how to install fromcvs
> would be helpful. I remember it was not obvious to me.
[..]
> I think a step by step explanation how to proceed would have helped me.

Could you write down what you had to do and where the problems are as an
extension to the current README?

Thanks,
  simon

  reply	other threads:[~2007-09-22 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20070920T010842-272@post.gmane.org>
2007-09-21  1:17 ` cvsimport bug on branches [was: conversion to git] Eric Blake
2007-09-21  5:18   ` Steffen Prohaska
2007-09-21 15:42     ` Linus Torvalds
2007-09-21 17:15       ` Robin Rosenberg
2007-09-21 20:22         ` Johannes Schindelin
2007-09-21 20:42           ` Robin Rosenberg
2007-09-21 21:12             ` Johannes Schindelin
2007-09-21 23:16               ` Robin Rosenberg
2007-09-22  8:07                 ` fromcvs installation [was: cvsimport bug on branches [was: conversion to git]] Steffen Prohaska
2007-09-22 15:08                   ` Simon 'corecode' Schubert [this message]
2007-09-22  0:05       ` cvsimport bug on branches [was: conversion to git] 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=46F5300B.2000707@fs.ei.tum.de \
    --to=corecode@fs.ei.tum.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=prohaska@zib.de \
    --cc=robin.rosenberg.lists@dewire.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).