From: "Jason Sewall" <jasonsewall@gmail.com>
To: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Test #7 in t9200-git-cvsexportcommit fails
Date: Sun, 22 Jul 2007 12:41:53 -0700 [thread overview]
Message-ID: <31e9dd080707221241j5c00aaaaqa79c12d3e2a3345b@mail.gmail.com> (raw)
This test fails for me on the current head (pulled just now) and where
the test was introduced (e86ad71fe).
All other tests pass.
I know almost nothing about how CVS works internally, so I don't have
any insight as to the cause of this problem - all I can see is that
the contents of CVS/Entries has the 'with spaces' files at 1.1 instead
of the expect 1.2.
I'm happy to provide more information if you can tell me how to get
it. In particular, I'd like to tell you about my version of perl-cvs
(or whatever it's called) but I have no idea how to do that...
Jason
P.S. I don't use this part of git at all, so this is not a priority
for me. I am using Fedora 7, which is definitely a mainstream distro,
so I imagine others might have this problem too.
next reply other threads:[~2007-07-22 19:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 19:41 Jason Sewall [this message]
2007-07-22 20:21 ` Test #7 in t9200-git-cvsexportcommit fails Alex Riesen
2007-07-22 20:49 ` Jason Sewall
2007-07-22 21:42 ` Alex Riesen
2007-07-22 22:19 ` Junio C Hamano
2007-07-23 3:59 ` [PATCH] Add a 1-second sleep to git-cvsexportcommit test Jason Sewall
2007-07-23 4:32 ` Junio C Hamano
2007-07-23 7:55 ` Simon 'corecode' Schubert
2007-07-24 0:23 ` Robin Rosenberg
2007-07-24 8:11 ` Simon 'corecode' Schubert
2007-07-24 8:33 ` Robin Rosenberg
2007-07-24 8:38 ` Simon 'corecode' Schubert
2007-07-24 9:34 ` Robin Rosenberg
2007-07-24 10:14 ` Junio C Hamano
2007-07-24 12:57 ` Robin Rosenberg
2007-07-24 15:31 ` Jason Sewall
2007-07-24 19:02 ` Linus Torvalds
2007-07-24 22:56 ` Robin Rosenberg
2007-07-24 23:19 ` Linus Torvalds
2007-07-25 7:35 ` Andy Parkins
2007-07-25 7:43 ` Marius Storm-Olsen
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=31e9dd080707221241j5c00aaaaqa79c12d3e2a3345b@mail.gmail.com \
--to=jasonsewall@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).