From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFA] gdb_ari.sh changes to discard some file types for specific tests
Date: Fri, 26 Oct 2007 09:44:00 -0000 [thread overview]
Message-ID: <ur6jirzg0.fsf@gnu.org> (raw)
In-Reply-To: <002501c817a0$82935900$87ba0b00$@u-strasbg.fr> (muller@ics.u-strasbg.fr)
> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: <drow@false.org>, <gdb-patches@sourceware.org>
> Date: Fri, 26 Oct 2007 09:19:12 +0200
>
> > > From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> > > Cc: <gdb-patches@sourceware.org>
> > > Date: Thu, 25 Oct 2007 09:17:54 +0200
> > >
> > > I changed the output of doscheck to
> > > avoid getting false duplicates for files
> > > in different directories.
> >
> > What are those false duplicates? can you show an example?
> >
> > I use doschk quite frequently, but never met such false duplicates.
>
> The errors are not in doscheck itself, but in the
> way the resulting data is handled in update_web_ari
Well, you did say that you fixed doschk...
> which will put together duplicates like
> gdb/ChangeLog and gdb/ChangeLog-2006
> and
> opcodes/ChangeLog and opcodes/ChangeLog-2006
> into a single CHANGELO entry.
That's true, but so what? The output clearly states the directory of
each file, doesn't it?
> No, the question was:
> how are the zip files for the sources of the DJGPP port of
> GDB produced?
Ah, sorry for misunderstanding. The omission of source directories is
manual.
prev parent reply other threads:[~2007-10-26 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:56 Pierre Muller
2007-10-24 20:29 ` 'Daniel Jacobowitz'
2007-10-25 7:22 ` Pierre Muller
2007-10-25 13:23 ` 'Daniel Jacobowitz'
2007-10-25 21:55 ` Eli Zaretskii
2007-10-25 22:10 ` Eli Zaretskii
2007-10-26 7:44 ` Pierre Muller
2007-10-26 9:44 ` Eli Zaretskii [this message]
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=ur6jirzg0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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