[Dev] [openssl] upstream branch update

Whiteman, John L john.l.whiteman at intel.com
Mon Oct 20 17:04:25 GMT 2014

Hi Janusz,

I'm fine with the second approach.  Other upstream packages are already
doing it and the history can be useful.

Best Regards,


-----Original Message-----
From: Janusz Kozerski [mailto:j.kozerski at samsung.com] 
Sent: Monday, October 20, 2014 6:38 AM
To: dev at lists.tizen.org
Cc: Tomasz Swierczek; Bartlomiej Grzelewski; Whiteman, John L; Demeter,
Subject: [openssl] upstream branch update

Hi All,

I've seen that on platform/upstream/openssl repository on upstream branch,
changes are pulled from upstream as a one big blob of code. Wouldn't be
better if we pull commits from upstream as they are? We can have full git
history instead of these blobs.

I've pushed to a review a commit with update to 1.0.1j in existing

I've also prepared a sandbox branch with the same upstream changes (with
full git history) rebased on tizen.org upstream branch:

We should choose one way of moving changes from upstream.
We should do the same for tizen branch.

Janusz Kozerski

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6664 bytes
Desc: not available
URL: <http://lists.tizen.org/pipermail/dev/attachments/20141020/b9fb6997/attachment.p7s>

More information about the Dev mailing list