From: Mark Mitchell <mark@codesourcery.com>
To: jason-swarelist@molenda.com
Cc: bkoz@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000421232112U.mitchell@codesourcery.com> (raw)
In-Reply-To: <20000421180410.A20416@shell17.ba.best.com>
>>>>> "Jason" == Jason Molenda <jason-swarelist@molenda.com> writes:
Jason> On Fri, Apr 21, 2000 at 05:55:36PM -0700, Mark Mitchell
Jason> wrote:
>> I pointed out that doing it the way Benjamin did would cause a
>> loss of revision history; he seemed cool with that.
Jason> I think it's a mistake--good revision history is critical
Jason> in tracing the changes of a file, is often useful in
Jason> bug-hunting, and it won't take any real effort to retain
Jason> the history.
I have no strong feeling. If Benjamin wants to do the ,v thing,
that's cool with me.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
WARNING: multiple messages have this Message-ID
From: Mark Mitchell <mark@codesourcery.com>
To: jason-swarelist@molenda.com
Cc: bkoz@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: libstdc++-v3 module moved into egcs
Date: Fri, 21 Apr 2000 23:13:00 -0000 [thread overview]
Message-ID: <20000421232112U.mitchell@codesourcery.com> (raw)
Message-ID: <20000421231300.LRgLpQ-UbSlQJm_RLU41wKHXlYNj32PO4Vyxr2nNRyE@z> (raw)
In-Reply-To: <20000421180410.A20416@shell17.ba.best.com>
>>>>> "Jason" == Jason Molenda <jason-swarelist@molenda.com> writes:
Jason> On Fri, Apr 21, 2000 at 05:55:36PM -0700, Mark Mitchell
Jason> wrote:
>> I pointed out that doing it the way Benjamin did would cause a
>> loss of revision history; he seemed cool with that.
Jason> I think it's a mistake--good revision history is critical
Jason> in tracing the changes of a file, is often useful in
Jason> bug-hunting, and it won't take any real effort to retain
Jason> the history.
I have no strong feeling. If Benjamin wants to do the ,v thing,
that's cool with me.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Benjamin Kosnik
2000-04-21 15:11 ` Benjamin Kosnik
2000-12-30 6:08 ` Tom Tromey
2000-04-21 17:13 ` Tom Tromey
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:08 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-24 10:11 ` Tom Tromey
2000-12-30 6:08 ` Gerald Pfeifer
2000-04-26 14:56 ` Gerald Pfeifer
2000-12-30 6:08 ` Tom Tromey
2000-04-26 15:00 ` Tom Tromey
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:31 ` Jeffrey A Law
2000-12-30 6:08 ` Jason Molenda
2000-04-24 10:32 ` Jason Molenda
2000-12-30 6:08 ` Jeffrey A Law
2000-04-24 10:58 ` Jeffrey A Law
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:42 ` Mark Mitchell
2000-12-30 6:08 ` Jason Molenda
2000-04-21 17:35 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell
2000-04-21 17:47 ` Mark Mitchell
2000-12-30 6:08 ` Jason Molenda
2000-04-21 18:04 ` Jason Molenda
2000-12-30 6:08 ` Mark Mitchell [this message]
2000-04-21 23:13 ` Mark Mitchell
2000-12-30 6:08 ` Andrew Cagney
2000-04-21 23:29 ` Andrew Cagney
[not found] <39014BB3.B681D244@nabi.net>
2000-12-30 6:08 ` Benjamin Kosnik
2000-04-21 23:56 ` Benjamin Kosnik
-- strict thread matches above, loose matches on Subject: below --
2000-12-30 6:08 Benjamin Kosnik
2000-04-24 11:22 ` Benjamin Kosnik
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=20000421232112U.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=bkoz@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=overseers@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).