Re: [CryptoAPI-devel] Is keeping the patches available throughtheSF.net "Files" section beneficial?

[Justin C. <ju...@po...>]

Hi Herbert,

Herbert Valerio Riedel wrote:
> 
> On Tue, 5 Mar 2002, Justin Clift wrote:
> 
> > I can see what you mean with that.  Sounds like the web-page needs to
> > have a few more links, as I don't think we can put links from the
> > "Files" section on the sourceforge site.
> >
> > I don't understand why we can't have the the patches signed with the gpg
> > kernel.org signature, wherever they are for download.  Then again, I
> > haven't used gpg which probably explains why.  :)
> ...silly me, the sigs can just be copied from kernel.org C:-)
> 
> ...forget that argument... :)

Heh Heh Heh

That's alright.  At least it means it won't be harder to give people the
ability to verify the files they've got.  :)

> 
> there's only one thing now... the API changed a little bit for the
> unofficial testing patches, and only now has changed back to a backward
> compatible means... so please wait a little bit before adding files...

Ummm... oops.

I've just added most of them.  Still wondering how I should put the
loop-* files up, etc.

What I've done so far is have add packages to the existing "cryptoapi"
release.  And each package is a group of files.  i.e. :

2.4.18.1
patch-int-2.4.18.1.bz2
patch-int-2.4.18.1.bz2.sign
patch-int-2.4.18.1.gz
patch-int-2.4.18.1.gz.sign

2.4.18.0
patch-int-2.4.18.0.bz2
patch-int-2.4.18.0.bz2.sign
patch-int-2.4.18.0.gz
patch-int-2.4.18.0.gz.sign

2.4.17.0
patch-int-2.4.17.0.bz2
patch-int-2.4.17.0.bz2.sign
patch-int-2.4.17.0.gz
patch-int-2.4.17.0.gz.sign


I'm thinking I should copy the loop-hvr-2.4.16.0.patch file to each of
these, just because it'll make it easier for newcomers to understand,
and probably the loop-jari-2.4.16.0.patch too.

i.e.

2.4.18.1
loop-hvr-2.4.18.1.patch
loop-jari-2.4.18.1.patch
patch-int-2.4.18.1.bz2
patch-int-2.4.18.1.bz2.sign
patch-int-2.4.18.1.gz
patch-int-2.4.18.1.gz.sign

2.4.18.0
loop-hvr-2.4.18.0.patch
loop-jari-2.4.18.0.patch
patch-int-2.4.18.0.bz2
patch-int-2.4.18.0.bz2.sign
patch-int-2.4.18.0.gz
patch-int-2.4.18.0.gz.sign

2.4.17.0
loop-hvr-2.4.17.0.patch
loop-jari-2.4.17.0.patch
patch-int-2.4.17.0.bz2
patch-int-2.4.17.0.bz2.sign
patch-int-2.4.17.0.gz
patch-int-2.4.17.0.gz.sign

Does adding in these patches (and renumbering them so it's easy to
understand) make sense to you?

:-)

Regards and best wishes,

Justin Clift

 
> regards,
> --
> Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
> Email: hv...@hv...       /    Finger hv...@gn... for GnuPG Public Key
> GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F 4142

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi