From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Problems Importing a CVS tree into FAUmachine
Date: Mon, 25 Jul 2005 11:20:20 +0200 [thread overview]
Message-ID: <20050725092020.GC25825@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050725091505.GA5680@kiste.smurf.noris.de>
Hello,
> If there's no lib/pattern-matcher/input/Pic0.ppm,v nor
> lib/pattern-matcher/input/Attic/Pic0.ppm,v file ...
no there isn't.
> ... then, congratulations, you've found a bug in cvsps. Please talk
> to its author.
yes, it seems so. My currently theory is that cvsps extracts the
information out of the log message of the Pic1.ppm file. However I
wonder why my grep didn't came with something up.
Thomas
next prev parent reply other threads:[~2005-07-25 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 20:56 Problems Importing a CVS tree into FAUmachine Thomas Glanzmann
2005-07-25 8:57 ` Thomas Glanzmann
2005-07-25 9:03 ` Thomas Glanzmann
2005-07-25 9:15 ` Matthias Urlichs
2005-07-25 9:20 ` Thomas Glanzmann [this message]
2005-07-25 9:41 ` Thomas Glanzmann
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=20050725092020.GC25825@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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