From: Junio C Hamano <gitster@pobox.com>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.4-rc3
Date: Fri, 11 Jan 2008 23:34:34 -0800 [thread overview]
Message-ID: <7vejcnwl85.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200801120926.14307.ismail@pardus.org.tr> (Ismail Dönmez's message of "Sat, 12 Jan 2008 09:26:14 +0200")
Ismail Dönmez <ismail@pardus.org.tr> writes:
> Saturday 12 January 2008 09:11:23 tarihinde Junio C Hamano şunları yazmıştı:
>> The third rc for the next feature release GIT 1.5.4 is available
>> at the usual places:
>>
>> http://www.kernel.org/pub/software/scm/git/
>>
>> git-1.5.4.rc3.tar.{gz,bz2} (tarball)
>> git-htmldocs-1.5.4.rc3.tar.{gz,bz2} (preformatted docs)
>> git-manpages-1.5.4.rc3.tar.{gz,bz2} (preformatted docs)
>> testing/git-*-1.5.4.rc3-1.$arch.rpm (RPM)
>
> I am seeing new failures compared to rc2 :
>
> *** t9200-git-cvsexportcommit.sh ***
> * FAIL 1: New file
> mkdir A B C D E F &&
> echo hello1 >A/newfile1.txt &&
> echo hello2 >B/newfile2.txt &&
> cp ../test9200a.png C/newfile3.png &&
> cp ../test9200a.png D/newfile4.png &&
> git add A/newfile1.txt &&
> git add B/newfile2.txt &&
> git add C/newfile3.png &&
> git add D/newfile4.png &&
> git commit -a -m "Test: New file" &&
> id=$(git rev-list --max-count=1 HEAD) &&
> (cd "$CVSWORK" &&
> git cvsexportcommit -c $id &&
> check_entries A "newfile1.txt/1.1/" &&
> check_entries B "newfile2.txt/1.1/" &&
> check_entries C "newfile3.png/1.1/-kb" &&
> check_entries D "newfile4.png/1.1/-kb" &&
> diff A/newfile1.txt ../A/newfile1.txt &&
> diff B/newfile2.txt ../B/newfile2.txt &&
> diff C/newfile3.png ../C/newfile3.png &&
> diff D/newfile4.png ../D/newfile4.png
> )
> Ideas appreciated.
Often the first failure is the most interesting one. Running
the test under sh -x like this:
$ cd t
$ sh t9200-git-cvsexportcommit.sh -i -v
and then looking at "trash" directory would tell you which one
of the long sequence of commands failed, and further
investigation can be made from there.
Thanks.
next prev parent reply other threads:[~2008-01-12 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 7:11 [ANNOUNCE] GIT 1.5.4-rc3 Junio C Hamano
2008-01-12 7:26 ` Ismail Dönmez
2008-01-12 7:34 ` Junio C Hamano [this message]
2008-01-21 2:37 ` [ANNOUNCE] GIT 1.5.4-rc4 Junio C Hamano
2008-01-28 10:56 ` [ANNOUNCE] GIT 1.5.4-rc5 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=7vejcnwl85.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.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