From: Hans-Peter Nilsson <hp@bitrange.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: sim checkout broken (was: [PATCH v5] don't keep a gdb-specific date)
Date: Wed, 26 Jun 2013 11:23:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1306260702510.73224@arjuna.pair.com> (raw)
In-Reply-To: <87bo6ute8b.fsf@fleche.redhat.com>
On Tue, 25 Jun 2013, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Tom> I'm going to try updating CVSROOT/modules and then check out some old
> Tom> branches, and see what happens. Please bear with me. I'll revert that
> Tom> change if it causes a problem.
>
> As far as I can tell, this works ok.
> You get one more non-fatal warning when checking out an old branch of "sim".
> However, seeing that there are already such warnings in a sim checkout,
> I don't think this is a problem.
There was talk about doing something with the CVS modules making
up sim, and it looks like someone did: something CVS-specific
has been done resulting in sim checkout now broken (at least for
the admittedly old 1.11.5), whereas checkout (as such) before
that wasn't broken.
Last time a checkout worked was 2013-06-25-00:13:53 UTC, like
so, with the last lines of the output being:
... (more "U"s elided)
U src/include/elf/mips.h
cvs checkout: warning: src/config.if is not (any longer) pertinent
cvs checkout: warning: src/configure.in is not (any longer) pertinent
cvs checkout: warning: src/gettext.m4 is not (any longer) pertinent
cvs checkout: warning: src/ltcf-c.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-cxx.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-gcj.sh is not (any longer) pertinent
cvs checkout: warning: src/ltconfig is not (any longer) pertinent
cvs checkout: warning: src/gdb/version.in is not (any longer) pertinent
(Though the cvs exit value 0 and fine.)
Then at 2013-06-25-18:03:41 UTC:
... (even more "U"s elided)
U src/include/opcode/mips.h
cvs checkout: warning: src/config.if is not (any longer) pertinent
cvs checkout: warning: src/configure.in is not (any longer) pertinent
cvs checkout: warning: src/gettext.m4 is not (any longer) pertinent
cvs checkout: warning: src/ltcf-c.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-cxx.sh is not (any longer) pertinent
cvs checkout: warning: src/ltcf-gcj.sh is not (any longer) pertinent
cvs checkout: warning: src/ltconfig is not (any longer) pertinent
cvs checkout: existing repository /cvs/src/CVSROOT/Emptydir does not match /cvs/src/src/gdb
cvs checkout: ignoring module src/gdb/version.in
(Here, the cvs exit value is indicating badness, as in
make: *** [update] Error 1
)
Can the action causing that Emptydir please be reverted?
And/or explained, maybe with a line indicating "better
switch to CVS-N.M".
Sorry for implicating you guys, but it's likely you know what
might have happened. At least more so than I, at the moment. :)
brgds, H-P
next prev parent reply other threads:[~2013-06-26 11:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 17:33 [PATCH v5] don't keep a gdb-specific date Tom Tromey
2013-06-21 18:00 ` Pedro Alves
2013-06-24 14:56 ` Tom Tromey
2013-06-24 19:22 ` Joel Brobecker
2013-06-24 22:41 ` [commit] Fix host_name and target_name generation by common/create-version.sh Joel Brobecker
2013-06-24 22:59 ` [PATCH v5] don't keep a gdb-specific date Joel Brobecker
2013-06-24 23:58 ` [commit] Adapt sim to new version number & date locations Joel Brobecker
2013-06-25 0:52 ` Mike Frysinger
2013-06-25 1:53 ` Joel Brobecker
2013-06-25 15:51 ` Tom Tromey
2013-06-25 15:57 ` Tom Tromey
2013-06-25 15:46 ` Tom Tromey
2013-06-25 16:01 ` Eli Zaretskii
2013-06-25 15:28 ` Tom Tromey
2013-06-25 16:41 ` Mike Frysinger
2013-06-25 1:08 ` [PATCH v5] don't keep a gdb-specific date Hans-Peter Nilsson
2013-06-25 14:16 ` Tom Tromey
2013-06-25 14:25 ` Joel Brobecker
2013-06-25 14:43 ` Tom Tromey
2013-06-25 15:27 ` Tom Tromey
2013-06-26 11:23 ` Hans-Peter Nilsson [this message]
2013-06-26 16:52 ` sim checkout broken Tom Tromey
2013-06-26 17:58 ` Hans-Peter Nilsson
2013-06-27 3:22 ` Tom Tromey
2013-06-27 4:05 ` Hans-Peter Nilsson
2013-06-27 15:22 ` Tom Tromey
2013-06-27 16:30 ` Tom Tromey
2013-06-27 17:09 ` RFC: move common/version.in to gdb/ (Was: sim checkout broken) Tom Tromey
2013-06-28 3:18 ` Hans-Peter Nilsson
2013-06-28 18:17 ` RFC: move common/version.in to gdb/ Tom Tromey
2013-06-27 17:27 ` sim checkout broken Hans-Peter Nilsson
2013-06-27 8:19 ` Andreas Schwab
2013-06-25 14:50 ` [PATCH v5] don't keep a gdb-specific date Pedro Alves
2013-06-25 14:53 ` Joel Brobecker
2013-06-25 15:01 ` Tom Tromey
2013-06-25 15:14 ` Pedro Alves
2013-06-26 2:45 ` Yao Qi
2013-06-26 16:06 ` Tom Tromey
2013-06-27 2:11 ` Yao Qi
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=alpine.BSF.2.02.1306260702510.73224@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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