Hi Bernd!

> at some point diff files have to be offered against current kernel 2035 
> sources.
> those would be huge, and some expert has to review them before committing.
> it's no use sending 1000 small patches. Only huge diff's will do now.

See below. Strong disagree!

> *kernel 2035A                    - only essential fixes, looks like Eric 
> now found some FORMAT/bootsector issues.

Not FORMAT, but processing of UNFORMATTED but PARTITIONED (or floppy) drives.
See my other mail for details.

> *kernel 2035+ -ARKADY - experimental kernel (because not tested in-the-wild)

Lucho has a copy of the binary online -> write a newsitem as soon as some
interesting and useful changes have accumulated, post it on FreeDOS.org ->
many people can test the kernel in the wild. You can / should also include
a "cutting edge" kernel with the next distro, but not preinstall it. Then
people can decide to use it if they prefer optimization over "testedness".
That way they can help us by testing, without having to download a separate file...

> people don't have time to daily review your patches. Send them once a 
> month, or put all patches also in a zip-archive for download.

I think you misunderstand the idea of patches. A patch tells you how to
change a SMALL amount of code, to improve ONE thing. A patchset contains
many small patches. People can download the patchset, and review one patch
after the other. Then they can include SOME of the patches in the CVS, as
soon as they have reviewed and tested them. If you have only few, big files
in that ZIP, then you can no longer separate good from bad patches. Then you
no longer win anything compared to downloading the Arkady version of the
sources as they are after patching.

If you have 10 small patches which all apply to the same single .c file,
than downloading the .c file is smaller than the 10 patches. BUT if you want
to figure out which of those 10 patches are good for you, then you MUST have
all 10 patches available as separate .diff files, which you can then apply
to the .c file with help of the "patch" tool (.diff files are created with
the "diff" tool, by the way, and both are available on the DJGPP homepage...).

Compare for exapmle with the DOSEMU patches: People submit them one by one,
and only after they are all reviewed and accepted, they are bundled. But even
then the patchset is split - for example the TGZ which updates one version of
the DOSEMU sources to the next version could contain one not-so-small diff file
which patches all sound-related things, one for the VGA emulation, and so on.

Patches are also sorted into patches which are accepted for DOSEMU stable and
patches which are available only for DOSEMU devel. You get the point :-).

Eric.



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to