Doc fix: Update Cargo.toml in book/getting-started

[deepak]

The Cargo.toml mentioned in book/getting-started
is missing the section called [dependencies]

fixes#32928

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[GuillaumeGomez]

I find this sentence a bit awkward. What about "Do not worry about the [dependencies] line, we will come back to it later."?

[deepak]

thanks. reads better.
have made the change and rebased

[GuillaumeGomez]

Thanks!

r=me @steveklabnik

[steveklabnik]

@bors: delegate=@GuillaumeGomez

[bors]

✌️ @@GuillaumeGomez can now approve this pull request

[bors]

📌 Commit 722faa0 has been approved by guillaumegomez

[steveklabnik]

whoops

@bors: delegate=GuillaumeGomez

[bors]

✌️ @GuillaumeGomez can now approve this pull request

[steveklabnik]

@bors: r=GuillaumeGomez

[bors]

💡 This pull request was already approved, no need to approve it again.

• There's another pull request that is currently being tested, blocking this pull request: Do not rely on file extensions after path canonicalization. #32828

[bors]

📌 Commit 722faa0 has been approved by GuillaumeGomez

[bors]

⌛ Testing commit 722faa0 with merge 21161a4...

[bors]

💔 Test failed - auto-win-gnu-32-opt

[alexcrichton]

@bors: retry

On Thu, Apr 14, 2016 at 12:26 PM, bors notifications@github.com wrote:

[image: 💔] Test failed - auto-win-gnu-32-opt
http://buildbot.rust-lang.org/builders/auto-win-gnu-32-opt/builds/3790

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#32931 (comment)