In regard to: Re: TODO for 1.2 release, Moses P. Milazzo said (at 4:28pm on...:
>> Better:
>>
>> find . -name '*.c' -o -name '*.h' -exec egrep '//' {} /dev/null \; | \
>> grep -v '://'
>>
>> (to get rid of false
"Moses P. Milazzo" wrote:
> Why not:
>
> grep "//" `find . -name "*.[ch]"` | grep -v 'p://'
You should include -print as part of the find statement or else you will
wind up getting a list of lines containing C++ style comments without
knowing the name of the file that needs to be edited.
Cheers
> Better:
>
> find . -name '*.c' -o -name '*.h' -exec egrep '//' {} /dev/null \; | \
> grep -v '://'
>
> (to get rid of false matches on URLs)
Why not:
grep "//" `find . -name "*.[ch]"` | grep -v 'p://'
(the -o option doesn't seem to work as advertised in the man page)
Don't forget that
[EMAIL PROTECTED] wrote:
> On 26 Sep, Tim Mooney wrote:
> >> Grepped through the source and couldn't find any C++ style
> >> comments...
>
> > cc: Error: lighting_ui.c, line 387: Invalid statement. (badstmt)
> > // GtkWidget *spinbutton;
> > --^
There are a number of C++ style comments. I ran
In regard to: Re: TODO for 1.2 release, Austin Donnelly said (at 11:35pm on...:
>On Tuesday, 26 Sep 2000, Tim Mooney wrote:
>
>> @@ -2322,6 +2322,7 @@
>>G_IO_ERROR_NONE,
>>G_IO_ERROR_AGAIN,
>>G_IO_ERROR_INVAL,
>> + G_IO_ERROR_INTR,
>>
On Tuesday, 26 Sep 2000, Tim Mooney wrote:
> @@ -2322,6 +2322,7 @@
>G_IO_ERROR_NONE,
>G_IO_ERROR_AGAIN,
>G_IO_ERROR_INVAL,
> + G_IO_ERROR_INTR,
>G_IO_ERROR_UNKNOWN
> } GIOError;
This breaks backwards binary compatibility, since the numeric value of
G_IO_ERROR_UNKNOWN changes.
On 26 Sep, Tim Mooney wrote:
> You need to quote the '*.c', it's getting expanded by the shell before
> it ever gets fed to find. :-)
Actually that's not the problem since there are no *.c files in the
directory I started the search in...
Anita:/mnt2/src/gimp # find -name *.c
./libgimp/gimps
In regard to: Re: TODO for 1.2 release, [EMAIL PROTECTED] said (at 12:19am on...:
>> Perhaps it's been fixed in CVS already, and that's what you're looking
>> at?
>
> No, it's not fixed in CVS but for some reason
> find -name *.c | grep "//&quo
On 26 Sep, Tim Mooney wrote:
>> Grepped through the source and couldn't find any C++ style
>> comments...
> cc: Error: lighting_ui.c, line 387: Invalid statement. (badstmt)
> // GtkWidget *spinbutton;
> --^
> This is from 1.1.26/plug-ins/Lighting. I haven't made the build
> proceed any far
In regard to: Re: TODO for 1.2 release, [EMAIL PROTECTED] said (at 12:05am on...:
>On 26 Sep, Tim Mooney wrote:
>
>> I'll try build 1.1.26 or some subsequent release on the platforms I
>> have access to, but whoever does pre-release builds (Yosh?) should see
>>
On 26 Sep, Tim Mooney wrote:
> I'll try build 1.1.26 or some subsequent release on the platforms I
> have access to, but whoever does pre-release builds (Yosh?) should see
> if there's a way to make your compiler (gcc?) warn/error on C++ style
> comments. Every single point build of gimp for the
On Tuesday, 26 Sep 2000, Tim Janik wrote:
> i think austin even had a patch for this, i'd love to include
> it into glib and release 1.2.9 for gimpers. though, what exact
> date do you have in mind for 1.2.0?
> i don't have austin's email handy, so i'd apprechiate if anyone
> would forward this e
On Tue, 26 Sep 2000, Tim Mooney wrote:
> In regard to: Re: TODO for 1.2 release, Garry R. Osgood said (at 5:38am on...:
>
> >Nick Lamb wrote:
> >
> >>
> >> Enough hilarity. If you know of something which must be done before
> >> 1.2.0 please follow
In regard to: TODO for 1.2 release, Nick Lamb said (at 8:21pm on Sep 25, 2000):
>Now, I bet a lot of money that Gimp 1.2 wouldn't be released in 2000
>To make me lose,
I still remember the announcement for the pre-1.0 party, where S
uttered the famous words, "One-point-Oh is
In regard to: Re: TODO for 1.2 release, Garry R. Osgood said (at 5:38am on...:
>Nick Lamb wrote:
>
>>
>> Enough hilarity. If you know of something which must be done before
>> 1.2.0 please follow on to this mail. If you know of a reason why
>> we should unfreeze
I need to squeeze a little time out of my currently hectic schedule to
go back and finish proofreading the help docs. I now have CVS access so
I just need to find time and learn how to use CVS and it won't be bad on
my part. (if anyone cares about docs that is)
bex
ps--i know i havent been on IR
Austin Donnelly wrote:
>
> B: Plugins
> --
>
> For plugins, I think we need to take some tough decisions as to which
> plugins are supported, and which aren't. I don't know how to do this,
> but others have suggested looking at which are mentioned in the
> MAINTAINERS file.
I would pe
On Monday, 25 Sep 2000, Nick Lamb wrote:
> 1. VAGUE: Documentation should be "good" (definition anyone?)
> 2. Critical/ Severe bug reports should be fixed or marked down (bug #s?)
> 3. VAGUE: Gimp should build out-of-box on lots of systems
> 99. Find and #ifdef any debug scribble to console
> 100
Nick Lamb wrote:
>
> Enough hilarity. If you know of something which must be done before
> 1.2.0 please follow on to this mail. If you know of a reason why
> we should unfreeze Gimp instead, feel free to let loose.
>
> 1. VAGUE: Documentation should be "good" (definition anyone?)
> 2. Critical/ S
Date: Mon, 25 Sep 2000 20:21:45 +0100
From: Nick Lamb <[EMAIL PROTECTED]>
Enough hilarity. If you know of something which must be done before
1.2.0 please follow on to this mail. If you know of a reason why
we should unfreeze Gimp instead, feel free to let loose.
I would like to g
Right, one of the formal things Linus' little toy project does which
allows him to ship only a year or two late is to have a list of stuff
that needs doing before release. Of course, none of that stuff gets
done, but you can document it and move on. Another toy project, named
after that monster w
21 matches
Mail list logo
