profile
viewpoint

HuKeping/30dayMakeOS 0

《30天自制操作系统》源码中文版。自己制作一个操作系统(OSASK)的过程

HuKeping/adt-tools-base 0

3rd party tools used by Android Plugin for IntelliJ IDEA

HuKeping/arm-trusted-firmware 0

Trusted Firmware-A

HuKeping/bazel 0

a fast, scalable, multi-language and extensible build system

HuKeping/cJSON 0

Ultralightweight JSON parser in ANSI C

HuKeping/configs 0

A repository to hold some configurations

HuKeping/containerd 0

A daemon to control runC

HuKeping/cri-o 0

Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

HuKeping/distribution 0

The Docker toolset to pack, ship, store, and deliver content

HuKeping/docker 0

Docker - the open-source application container engine

push eventHuKeping/upstream

Hu Keping

commit sha d145e081f842c8482c1dcae611a0ae04fc732498

Introduce some Python projects Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 16 hours

PR merged HuKeping/upstream

Explain prefix in README

Signed-off-by: Hu Keping hukeping@huawei.com

+5 -0

0 comment

1 changed file

HuKeping

pr closed time in 2 days

push eventHuKeping/upstream

Hu Keping

commit sha f4036540211e7bc772c6fae237234c5298bcace7

Explain prefix in README Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 2 days

push eventHuKeping/upstream

Hu Keping

commit sha 767a516a410c3002829e1d2f2eda4c5ade1d4c5b

Add pixman and keyutils Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

junedwx

commit sha bbf7fed8f0629bc04f1d119248a480ab3813233a

Merge pull request #3 from HuKeping/dev Add pixman and keyutils

view details

Hu Keping

commit sha f4036540211e7bc772c6fae237234c5298bcace7

Explain prefix in README Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 3 days

PR opened HuKeping/upstream

Explain prefix in README

Signed-off-by: Hu Keping hukeping@huawei.com

+5 -0

0 comment

1 changed file

pr created time in 3 days

create barnchHuKeping/upstream

branch : readme

created branch time in 3 days

push eventHuKeping/upstream

Hu Keping

commit sha 767a516a410c3002829e1d2f2eda4c5ade1d4c5b

Add pixman and keyutils Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 3 days

pull request commentHuKeping/upstream

Add pixman and keyutils

@junedwx PTAL

HuKeping

comment created time in 3 days

PR opened HuKeping/upstream

Add pixman and keyutils

Signed-off-by: Hu Keping hukeping@huawei.com

+8 -0

0 comment

1 changed file

pr created time in 3 days

create barnchHuKeping/upstream

branch : dev

created branch time in 3 days

delete branch HuKeping/upstream

delete branch : dev

delete time in 3 days

push eventHuKeping/upstream

Hu Keping

commit sha 008beb37c038e3b65c4811d36aec7d424b37df08

Init upstream.yaml Introduce cJSON as the first item and add a script to check if all the upstream repo were reachable. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

Hu Keping

commit sha 930fc046f436716bb484c9736c0c08f4dc70ef7a

Introduce travis CI Validate every upstream to see if it was reachable via git clone. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

Hu Keping

commit sha 530a378284fc8ce3a5ad497422fb47e1a3f9493c

Add bzip2 Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 4 days

push eventHuKeping/upstream

Hu Keping

commit sha 008beb37c038e3b65c4811d36aec7d424b37df08

Init upstream.yaml Introduce cJSON as the first item and add a script to check if all the upstream repo were reachable. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

Hu Keping

commit sha 930fc046f436716bb484c9736c0c08f4dc70ef7a

Introduce travis CI Validate every upstream to see if it was reachable via git clone. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 4 days

issue commentopenssl/openssl

3.0.0-alpha4: different compression level between distribution tarballs

@levitte As per the manual of git archive, attributes are by default taken from the .gitattributes files in the tree that is being archived.

But with option --worktree-attributes enabled, git archive will use the attribute file in the current workspace instead of using the one in the source tree, eg:

# make a temp attribute file
$ echo "NEWS.md  export-ignore" >> .gitattributes

# without --worktree-attributes
$ git archive -o old.tar.gz openssl-3.0.0-alpha4

# with --worktree-attributes
$ git archive -o new.tar.gz --worktree-attributes openssl-3.0.0-alpha4

# you will find the NEWS.md was removed in new.tar.gz
$ vimdiff    old.tar.gz    new.tar.gz

With this option, it will be more likely to make a wrong tarball especially when you are not on the right tree (git archive 3.0 but you're on 2.0, 1.0, master branch , etc).

HuKeping

comment created time in 4 days

push eventHuKeping/upstream

Hu Keping

commit sha 287cc0dad56046c5bd97f3857826c643582e90d9

Test travis CI Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

MemberEvent

PR opened HuKeping/upstream

Add bzip2

Signed-off-by: Hu Keping hukeping@huawei.com

+4 -0

0 comment

1 changed file

pr created time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 3fa53b20eb1cd8d96ee0059b5db3e1d90ec258fc

Add bzip2 Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

PR merged HuKeping/upstream

Init upstream.yaml

Introduce cJSON as the first item.

Signed-off-by: Hu Keping hukeping@huawei.com

+4 -0

0 comment

1 changed file

HuKeping

pr closed time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 02941c7c702ba374734ae1049d9e81d3aeeb516d

Init upstream.yaml Introduce cJSON as the first item. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 02941c7c702ba374734ae1049d9e81d3aeeb516d

Init upstream.yaml Introduce cJSON as the first item. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 18ddb30954bc57949d1c94fc8aea73dcceda8c43

Init upstream.yaml Introduce cJSON as the first item. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 9f75f62d1af46e268b15ae4ef5e68808ff6c6149

Introduce travis CI Validate every upstream to see if it was reachable via git clone. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

Hu Keping

commit sha a854a5a53025492cb6b7c245f9b939c621b4f7db

Init upstream.yaml Introduce cJSON as the first item. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

push eventHuKeping/upstream

Hu Keping

commit sha 9f75f62d1af46e268b15ae4ef5e68808ff6c6149

Introduce travis CI Validate every upstream to see if it was reachable via git clone. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 5 days

PR opened HuKeping/upstream

Init upstream.yaml

Introduce cJSON as the first item.

Signed-off-by: Hu Keping hukeping@huawei.com

+4 -0

0 comment

1 changed file

pr created time in 5 days

create barnchHuKeping/upstream

branch : dev

created branch time in 5 days

create barnchHuKeping/upstream

branch : master

created branch time in 5 days

created repositoryHuKeping/upstream

Upstream information of open source projects.

created time in 5 days

issue commentopenssl/openssl

3.0.0-alpha4: different compression level between distribution tarballs

@levitte Thanks for the link of those discussions , it helps a lot.

I'm definitely agreed with you that it is not reasonable to assume that GitHub will (always) generated the distribution tarball as what we really wanted. The mktar.sh scripts we used is very explicit about how these distributions are created, and it works great.

But since we have everything versioned with git and use the tool(git archive) that comes with it, I think there is still one thing we could make a approve. See main part of the mktar.sh scripts :

 33  # This counts on .gitattributes to specify what files should be ignored
 34  git archive --worktree-attributes --format=tar --prefix="$NAME/" -v HEAD \
 35      | gzip -9 > "$TARFILE.gz"
 36 

Because the format will inferred from the output file and attributes are by default taken from the .gitattributes files in the tree that is being archived. We can make it more simple :

  git archive --prefix="$NAME/"  -o $TARFILE.tar.gz HEAD

As this if we would like to to provide zip file in the further, we can just change it as:

  git archive --prefix="$NAME/"  -o $TARFILE.zip HEAD

If the $TARFILE already contains the suffix, we can make it more general:

  git archive --prefix="$NAME/"  -o $TARFILE HEAD

If you think it's worth doing this, I can make a PR.

HuKeping

comment created time in 6 days

issue commentguanzhi/GmSSL

[建议]加强工程化支持

太好了。

J-Feng

comment created time in 12 days

issue closedguanzhi/GmSSL

我们的版本发布方式是什么

看到主页有 GmSSL-2.4.0 发布,但是在github上面没有对应的release tag节点?

2.4.0对应的应该是这个commit吧 f411936f9f4057713b16ee0304c164ee340b41ad?

我们是否可以发布一个正式的release tag?这样大家用起来可能会方便一些。

closed time in 12 days

HuKeping

issue commentguanzhi/GmSSL

我们的版本发布方式是什么

看到了FAQ issue:https://github.com/guanzhi/GmSSL/issues/610

关闭该issue。

HuKeping

comment created time in 12 days

issue openedguanzhi/GmSSL

我们的版本发布方式是什么

看到主页有 GmSSL-2.4.0 发布,但是在github上面没有对应的release tag节点?

看了一下代码历史,应该是这个commit吧 f411936f9f4057713b16ee0304c164ee340b41ad?

我们是否可以发布一个正式的release tag?

created time in 12 days

issue commentopenssl/openssl

3.0.0-alpha4: different compression level between distribution tarballs

So the release has openssl-3.0.0-alpha4 as directory, the github one openssl-openssl-3.0.0-alpha4

Correct, and you can make it the same if you try :

# tarball from release and md5sum
$ wget https://www.openssl.org/source/openssl-3.0.0-alpha4.tar.gz -O openssl-3.0.0-alpha4-release.tar.gz
$ md5sum openssl-3.0.0-alpha4-release.tar.gz
77b49cc5de23ef79a75a6d3aaa555b46  openssl-3.0.0-alpha4-release.tar.gz

# tarball from github and md5sum 
$ wget https://github.com/openssl/openssl/archive/openssl-3.0.0-alpha4.tar.gz -O openssl-3.0.0-alpha4-github.tar.gz
$ md5sum openssl-3.0.0-alpha4-github.tar.gz
cc82107365e76fec97a9d519b9c1f43d  openssl-3.0.0-alpha4-github.tar.gz


$ git clone https://github.com/openssl/openssl.git

# compare with tarball from github
$ git -C openssl archive -9 --prefix=openssl-3.0.0-alpha4/ -o ../openssl-3.0.0-alpha4-center.tar.gz openssl-3.0.0-alpha4
$ md5sum openssl-3.0.0-alpha4-center.tar.gz
77b49cc5de23ef79a75a6d3aaa555b46  openssl-3.0.0-alpha4-center.tar.gz

# comapre with tarball from release page
$ git -C openssl archive --prefix=openssl-openssl-3.0.0-alpha4/ -o ../openssl-openssl-3.0.0-alpha4-center.tar.gz openssl-3.0.0-alpha4
$ md5sum openssl-openssl-3.0.0-alpha4-center.tar.gz
cc82107365e76fec97a9d519b9c1f43d  openssl-openssl-3.0.0-alpha4-center.tar.gz
HuKeping

comment created time in 12 days

issue commentopenssl/openssl

3.0.0-alpha4: different compression level between distribution tarballs

I think that if you unpack the files from github, it will also contain different files.

Actually it's the same, the only difference between these two tarball is:

  • compression level
  • prefix, one is openssl-openssl-3.0.0-alpha4, the other is openssl-3.0.0-alpha4
$ mkdir openssl-3.0.0-alpha4-github openssl-3.0.0-alpha4-release
$ tar -zxf openssl-3.0.0-alpha4-github.tar.gz -C openssl-3.0.0-alpha4-github
$ tar -zxf openssl-3.0.0-alpha4-release.tar.gz -C openssl-3.0.0-alpha4-release
$ diff -r openssl-3.0.0-alpha4-github/openssl-openssl-3.0.0-alpha4 openssl-3.0.0-alpha4-release/openssl-3.0.0-alpha4
$
HuKeping

comment created time in 12 days

issue openedopenssl/openssl

3.0.0-alpha4: different compression level between distribution tarballs

<!-- Thank you for your interest in OpenSSL. If this is your first question, please take the time to read the following lines before posting it.

For general questions about using OpenSSL:

If you have questions about how to use OpenSSL for specific tasks
or how to solve certain problems you have when using it, you might
want to ask them on the openssl-users@openssl.org mailing list.
There you can get help from a great community of OpenSSL users,
not only (but including) the OpenSSL developers. For more information
about our mailing lists, see
https://www.openssl.org/community/mailinglists.html.

For questions related to build issues:

Please use the 'Bug report' template.

For other questions:

Please describe your problem as concisely as possible while giving
us enough information to understand your problem. Example code
or example commands are highly appreciated if they help us to
better understand what you are trying to achieve.

Also, please remember to tell us which OpenSSL version you are
using and whether it is system provided or you built it yourself.
In the latter case, please also send us your build configuration.
With OpenSSL before 1.1.1, the configuration output comes from the
configuration command.  With OpenSSL 1.1.1 and on, you can obtain
the information by running the command `perl configdata.pm --dump`
in the root directory of the source tree.

Please remember to put ``` lines before and after any commands plus output and code, like this:

```
$ echo output output output
output output output
```

```
#include <stdio.h>

int main() {
    int foo = 1;
    printf("%d\n", foo);
}
```

-->

Happy to see we've already simplified the method for producing tarballs, but why we use different compression level to created it?

$ wget https://www.openssl.org/source/openssl-3.0.0-alpha4.tar.gz -O openssl-3.0.0-alpha4-release.tar.gz
$ wget https://github.com/openssl/openssl/archive/openssl-3.0.0-alpha4.tar.gz -O openssl-3.0.0-alpha4-github.tar.gz

$ file openssl-3.0.0-alpha4-github.tar.gz
openssl-3.0.0-alpha4-github.tar.gz: gzip compressed data, from Unix

$ file openssl-3.0.0-alpha4-release.tar.gz
openssl-3.0.0-alpha4-release.tar.gz: gzip compressed data, max compression, from Unix

It seems we use git archive -9 to create the distribution tarball on the official download page, and github automatically create the one from source tree with git archive.

To make it consistent (official release page and github release page), would you mind if not using level 9 to create the distribution tarball on the official release page?

created time in 12 days

pull request commentOP-TEE/optee_os

Add .gitattributes

Commit message updated and re-pushed.

HuKeping

comment created time in 17 days

push eventHuKeping/optee_os

Hu Keping

commit sha dc617735610862a714900b496c8a744101df3558

Add .gitattributes This patch adds a .gitattributes file to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com> Acked-by: Etienne Carriere <etienne.carriere@linaro.org>

view details

push time in 17 days

push eventHuKeping/optee_os

Hu Keping

commit sha c07f2970f1abad54511e2bc1fb1a840a0f9c192b

Add .gitattributes This patch adds a .gitattributes file to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 18 days

PR opened OP-TEE/optee_os

Add .gitattributes

This patch adds a .gitattributes file to specify files that should never end up in a distribution tarball.

A similar change has been rised at https://github.com/OP-TEE/optee_client/pull/212

Signed-off-by: Hu Keping hukeping@huawei.com

<!-- If you are new to submitting pull requests to OP-TEE, then please have a look at the list below and tick them off before submitting the pull request.

1. Read our contribution guidelines:
     https://optee.readthedocs.io/en/latest/general/contribute.html

2. Read the contribution section in Notice.md and pay extra attention to the
   "Developer Certificate of Origin" in the contribution guidelines.

3. You should run checkpatch preferably before submitting the pull request.

4. When everything has been reviewed, you will need to squash, rebase and
   add tags like `Reviewed-by`, `Acked-by`, `Tested-by` etc. More details
   about this can also be found on the link provided above.

NOTE: This comment will not be shown in the pull request, so no harm keeping
it, but feel free to remove it if you like.

-->

+6 -0

0 comment

1 changed file

pr created time in 18 days

create barnchHuKeping/optee_os

branch : add-gitattribute

created branch time in 18 days

push eventHuKeping/optee_client

Hu Keping

commit sha b66480cd51d9bc957f16c77937b1b0c6d9bbaa4b

Add .gitattributes When creating a release tarball (we're using `git archive`), it's pointless to include .gitignore and scripts for travisCI. This patch adds a .gitattributes file to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com> Acked-by: Jerome Forissier <jerome@forissier.org> Acked-by: Etienne Carriere <etienne.carriere@linaro.org>

view details

push time in 18 days

pull request commentOP-TEE/optee_client

Update tarball makeing procedure

should I add the ack of @etienne-lms to the commit message and re-push it?

HuKeping

comment created time in 18 days

delete branch HuKeping/cJSON

delete branch : fix-git-archive

delete time in 18 days

PR opened DaveGamble/cJSON

Remove unnecessary files in release tarball

Prior to this patch, we would find '.gitignore', '.travisCI.yml' in the release tarball.

This patch adds a few entries in .gitattributes to specify files that should never end up in a distribution tarball.

Signed-off-by: Hu Keping hukeping@huawei.com

+7 -1

0 comment

1 changed file

pr created time in 20 days

create barnchHuKeping/cJSON

branch : fix-git-archive

created branch time in 20 days

release HuKeping/cJSON

v1.7.12

released time in 20 days

pull request commentOP-TEE/optee_client

Update tarball makeing procedure

Commit message updated, PTAL @jforissier

HuKeping

comment created time in 20 days

push eventHuKeping/optee_client

Hu Keping

commit sha ea5b79b36a0dc70a7eb0cd6664ad823fb35a3655

Add .gitattributes When creating a release tarball (we're using `git archive`), it's pointless to include .gitignore and scripts for travisCI. This patch adds a .gitattributes file to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com> Acked-by: Jerome Forissier <jerome@forissier.org>

view details

push time in 20 days

push eventHuKeping/optee_client

Hu Keping

commit sha bea938b1fc783540cb92b8d027624d616d2d8703

Update tarball making procedure When creating a release tarball(we're using `git archive`, if I'm right), it's pointless to include .gitignore and scripts for travisCI. This patch adds a few entries in .gitattributes to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 21 days

PR opened OP-TEE/optee_client

Update tarball makeing procedure

When creating a release tarball(we're using git archive, if I'm right), it's pointless to include .gitignore and scripts for travisCI.

This patch adds a few entries in .gitattributes to specify files that should never end up in a distribution tarball.

Signed-off-by: Hu Keping hukeping@huawei.com

+4 -0

0 comment

1 changed file

pr created time in 21 days

push eventHuKeping/optee_client

Hu Keping

commit sha 1c04b802da412a6fd97f077709b5e0484d5c015a

Update tarball makeing procedure When creating a release tarball(we're using `git archive`, if I'm right), it's pointless to include .gitignore and scripts for travisCI. This patch adds a few entries in .gitattributes to specify files that should never end up in a distribution tarball. Signed-off-by: Hu Keping <hukeping@huawei.com>

view details

push time in 21 days

create barnchHuKeping/optee_client

branch : add-gitattribute

created branch time in 21 days

issue openedadobe/XMP-Toolkit-SDK

Is this the main repo to develop XMP Toolkit SDK

Hi @Priyanka-Gupta @pawankishorsingh ,

At present people can only download the source of XMP ToolKit SDK from https://www.adobe.com/devnet/xmp.html .

I wonder if this git repo would be the main place to develop XMP Toolkit SDK, and is there any plan to introduce release tag?

created time in a month

issue openednmap/nmap

introduce release tag into this repo

Hi ,

Do we have any plan to introduce release tag in this git repo? It might be helpful especially when people use git to checkout the source code of nmap.

Maybe just transfer the tags from svn repo to here?

created time in 2 months

fork HuKeping/adt-tools-base

3rd party tools used by Android Plugin for IntelliJ IDEA

fork in 2 months

more