RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

http://mmmaybe.gimp.org changes

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.
http://mmmaybe.gimp.org changes Niklas Mattisson 01 Aug 18:42
  http://mmmaybe.gimp.org changes Joao S. O. Bueno 01 Aug 19:56
   http://mmmaybe.gimp.org changes Raphaël Quinet 04 Aug 21:47
Niklas Mattisson
2003-08-01 18:42:56 UTC (over 20 years ago)

http://mmmaybe.gimp.org changes

Hey everyone,

Me and a few others on the web-team thought it might be time for you to know a little more about what has happened to the site right now and what is going on with it. So here is a little statistics list of things being worked at and things that is being changed.

- MacOSX information are on the way and we Mat Caughron as the maintainer for the MacOSX section now. Thanks to Mat we also have screenshots also. So a great thanks goes to Mat because he has taken the time to write this information for w.g.o.

When the information is on the site then both me and Mat would like to have some feedback on the information that will be in the MacOSX section.

- Bugs have now changed to be a section with information and there is HOWTOs in that section now also. I wrote a "How To Submit a Patch" this weekend also and would like people to look at it and give me comments and some feedback to make it even better.

- Many cleanups and smaller changes has been worked out also. Though there is a few things like the Documents section that needs to be looked at also. I want to do as much cleaning up as possible to make the move easier and faster.

I have a list of things locally that we have to look at. But what I want to ask from you guys is to look at the site and report problems that might be trouble when we move the site to w.g.o.

We would have been more then happy to say that the site is ready as it is now but there is as you can see some small things that is going to be done and we hope to do them as fast as possible.

So please test things on the site and give us feedback about the tests.

Regards,

Joao S. O. Bueno
2003-08-01 19:56:23 UTC (over 20 years ago)

http://mmmaybe.gimp.org changes

Niklas Mattisson wrote:

- Bugs have now changed to be a section with information and there is HOWTOs in that section now also. I wrote a "How To Submit a Patch" this weekend also and would like people to look at it and give me comments and some feedback to make it even better.

Maybe you could add some information about witch switches to use on the diff command to create a suitable patch.

I know that it may be well known for everyone here, but I for an example, had to re-submit my first patch to the gimp because I've created it without the -p switch.

Regards, JS
->

Raphaël Quinet
2003-08-04 21:47:18 UTC (over 20 years ago)

http://mmmaybe.gimp.org changes

On Fri, 01 Aug 2003 14:56:23 -0300, "Joao S. O. Bueno" wrote:

Maybe you could add some information about witch switches to use on the diff command to create a suitable patch.

I know that it may be well known for everyone here, but I for an example, had to re-submit my first patch to the gimp because I've created it without the -p switch.

It should be emphasized that the best way to create a patch is to use "cvs diff" from a checked-out CVS tree. The paragraph that mentions this should remind the user that in order to use CVS efficiently, it is highly recommended to have a ~/.cvsrc file that contains at least the following settings:

diff -up
rdiff -up
update -Pd
checkout -P
co -P
get -P

The next paragraph would say that those who do not use CVS should generate their patches with "diff -up" (and maybe -b or -w). It could even be more verbose and remind the user that the correct syntax is: diff -up old_file new_file > patch_file And if the patch affects multiple files, a recursive diff is necessary, using the original source tree as a reference (i.e., from the latest tarball) and a second copy of the source tree for the modified code: diff -rup old_source_tree modified_source_tree > patch_file

-Raphaël