dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: Othelo v1.4 + Documentation

Re: Othelo v1.4 + Documentation

From: BlueChip <>
Date: Wed, 30 Jul 2003 21:11:16 +0100

> > >Uh, diff please? Patch tracker?
> >
> > Only doing what was asked of me.
> > Anybody else got any requests?
>I'm not writing this to whine. I really appriciate your code and efforts.

Thank you for those kind words. Thank you's are all so rare on this kind
of project.

>Actually, the CONTRIBUTE docs mention posting diffs to the patch tracker as
>the way to contribute code to the project.
>The reason I insist on this practise is both for your sake and for the sake of
>the ones who'll do the CVS operations:
> Contributors such as yourself tend to not like it when your efforts are
> forgotten or seemingly being ignored.

Absolutely, which is one of the reasons, I am "miffed" at my experiences so
far :(

There are no docs to say HOW to make a patch - I am a programmer, not a
bash guru.
Anyway, eventually, after being mislead a couple of time, I finally worked
it out and v1.1 of othelo was a .pat file.
The next thing I know, is that I go to post a comment about my patch - and
it is gone.
Pleasingly, it magically appeared as a plugin :)
...Minus it's documentation of the very first comments I was
criticised for making on this group was lack of useful docs! Especially
for the beginner!
So I endeavoured on a course to get the docs included.
After many attempts, I was told to upload the here, and whoever it was
would take care of the problem for me.
...I like help, so I sent the docs as requested.
...As I has also patched the code that night, it seemed sensible to attach
it with the relevant docs.

Should my last lot of work (eg. docs) be included (or excluded FOR A
REASON) then I will continue to work with whatever system made it happen.
If my persistence is futile, then I will just post the patches somewhere
else and email the URL to this list for those who may be interested - I am
sure I can come up with something sensible to put in the subject so that
interested parties can set up a filter :)

>This happens very easily when you
> post patches to the list only, as we're a high volume list with lots of
> traffic which makes it very easy to miss single patches.

I appreciate that fully> But having tried and failed with the official
system ...what's a girl to do?

> Having all the patches and code contributions in the patch tracker allows
> us to manage them much easier: they're not forgotten, we can prioritize
> them, we can assign them to a certain developer, etc.

Perhaps I fail to understand this "assigned" thing.

Anyway, there is another alternative, I learn to use CVS and request commit
privs ...IN THAT ORDER ;)

Cheers Dan. Your help is always appreciated :)

Received on 2003-07-30

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy