Add some links in config.md

[coolljt0725]

Signed-off-by: Lei Jitang leijitang@huawei.com

Link to Image ID defininion when it refer to Image ID in definition of Image JSON ,
and link to Image JSON when it refer configuration JSON in definition of Image ID to make
it more clear.

[wking]

I didn't expect this to work with GitHub's filesystem browser, since
it mutates the names to user-content-image_json and the like [1]. But
they must have some magic to handle the translation, because 2 puts
my Firefox at the right place. So I'm not sure how portable the
translation is, but f9f6696 looks good to me.

[1]: $ curl -s https://github.com/coolljt0725/image-spec/blob/f9f6696052cb0f9c20241064f7a34f658253bdb6/serialization.md | grep image_json
Image JSON
Each image's ID is given by the SHA256 hash of its configuration JSON.
Since the configuration JSON that gets hashed references hashes of each layer in the image, this formulation of the ImageID makes images content-addresable.

[jonboulle]

Needs a rebase.

[coolljt0725]

@jonboulle rebased

[wking]

28743f6 still looks good to me.

[vbatts]

LGTM

[philips]

Sorry, I stripped out all of the HTML in #333. And I personally don't feel these links add a ton of value and may break depending on how this doc is rendered.

[coolljt0725]

@philips Add these links to make it more readable . The description of Image JSON reference a ImageID defined below, it's better to link to there.

[wking]

On Tue, Sep 20, 2016 at 11:20:43PM -0700, Lei Jitang wrote:

@philips Add these links to make it more readable . The description
of Image JSON reference a ImageID defined below, it's better to
link to there.

You can link there with the Markdown in #333 (e.g. 1). I suggest
re-closing this PR in favor of #333.

[coolljt0725]

@wking I hope #333 could included this :)

[wking]

On Tue, Sep 20, 2016 at 11:55:58PM -0700, Lei Jitang wrote:

@wking I hope #333 could included this :)

#333 already adds the anchors. I've filed [1,2] asking for the links
themselves.