From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: Ugly little hack for snapshot problem
Date: Fri, 15 Aug 2003 21:28:00 -0000 [thread overview]
Message-ID: <20030815212811.GB2840@nevyn.them.org> (raw)
In-Reply-To: <200308152120.h7FLKVcn020381@duracef.shout.net>
On Fri, Aug 15, 2003 at 05:20:31PM -0400, Michael Elizabeth Chastain wrote:
> Now I've got a third idea. It's simple:
>
> src-release walks the tree and configures all the subdirs ...
> src-release walks the tree and makes 'distclean ...'
> + src-release calls 'rm -f dejagnu/example/calc/config.status'
>
> Advantages:
>
> It's very easily seen to be correct.
> It's very easily seen not to touch anything except src-release.
> It patches src-release, not dejagnu, so it doesn't get wiped
> by a dejagnu import.
> I can stick a comment in there so that if dejagnu evers gets fixed,
> and we import a new dejagnu, the kludge can go away soon after that.
Sounds fine. Could use it for intl too.
> Disadvantages:
>
> It's ugly.
> The top-level MAINTAINERS file does not say who owns 'src-release'.
>
> Like the cliche says: "if it's stupid, and it works, it isn't stupid."
>
> How about it?
GDB and binutils own src-release. As far as I'm concerned, it's
reasonable; let's see what others say.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-15 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 21:20 Michael Elizabeth Chastain
2003-08-15 21:28 ` Daniel Jacobowitz [this message]
2003-08-15 21:37 Michael Elizabeth Chastain
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=20030815212811.GB2840@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).