This is the mail archive of the
mailing list for the libstdc++ project.
Re: auto_ptr / iostream bugs
- From: Phil Edwards <phil at jaj dot com>
- To: Jack Reeves <jack_reeves at hispeed dot ch>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Wed, 3 Jul 2002 19:22:15 -0400
- Subject: Re: auto_ptr / iostream bugs
- References: <firstname.lastname@example.org>
Hope this is correct address to send to.
On Thu, Jul 04, 2002 at 01:06:36AM +0200, Jack Reeves wrote:
> Both submissions were against the 3.1 release code (I currently do not have CVS access
> although I hope to change that in a couple of weeks).
Okay. The patch will appear in both 3.1.1 and subsequent releases.
> For the iostreams stuff, I will go back and redo the patch into the standard form. It has been suggested
> that it was too large. I know it involved several files, but it was basically triggered all by one thing.
> Which would be the preference, individual patches - one per file - or one email with a bunch of
If you mean my response about whether you need paperwork on file with
the FSF, that isn't affected by the size of individual patch files.
Think "number of lines of code changed," if that makes it clearer.
The way you posted the patch was fine, except for the context diff thing
I mentioned. If you're sending diffs against the released source, then
all methods will be equally slightly inconvenient :-) but we can cope.
Once you get an anonymous CVS checkout, then you can make you changes
directly, and run
cvs diff -c3p include/bits/foo src/bar testsuite/blah > changes
http://gcc.gnu.org/contribute.html has good advice about how best to mail
the "changes" file (scroll down to the Submitting Patches part).
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams