On 2016-05-18 14:35, Elan Ruusamäe wrote:
On 18.05.2016 14:54, Arkadiusz Miśkiewicz wrote:
On Wednesday 18 of May 2016, Elan Ruusamäe wrote:
On 18.05.2016 14:18, arekm wrote:
commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c
Author: Arkadiusz Miśkiewicz<[email protected]>
Date: Wed May 18 13:16:40 2016 +0200
- rel 4; more upstream git branch updates
glibc-git.patch | 60944
------------------------------------------------------ glibc.spec
| 3 +-
why keep this git.patch in our git, why not upload to distfiles?
it's not like it's diff of .patch is something useful to look at.
Maybe not for you but I was ofter doing git diff and git log on patch
files
like this to see what has changed etc.
"log" seems to be mostly just "updated from upstream".
https://github.com/pld-linux/glibc/commits/master/glibc-git.patch
I hate those 'git patches' and 'updated from upstream' logs. That gives
no version information. I would prefer to see some snapshot / upstream
revision number, which I could use to check actual changes upstream.
Or full upstream patches, with their commit messages. The
'glibc-git.patch' with 'updated from upstream' logs is not much more
useful than a random binary blob.
Jacek
_______________________________________________
pld-devel-en mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
