From 9d480dcfde8c7c82119f029b07b4f5ab143c9ea2 Mon Sep 17 00:00:00 2001 From: Alexey Palazhchenko Date: Mon, 28 Aug 2017 22:19:12 +0300 Subject: [PATCH] Expand FAQ entry --- docs/FAQ.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 24ee7f9b97..574c5a42ae 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -296,13 +296,13 @@ It's up to you: **Pros** -- it's the only way to get truly reproducible builds, as it guards against upstream renames and deletes -- you don't need an extra `dep ensure` step (to fetch dependencies) on fresh clones to build your repo +- It's the only way to get truly reproducible builds, as it guards against upstream renames, deletes and commit history overwrites. +- You don't need an extra `dep ensure` step (to fetch dependencies) on fresh clones to build your repo: you can use `go get` as usual. **Cons** -- your repo will be bigger, potentially a lot bigger -- PR diffs are more annoying +- Your repo will be bigger, potentially a lot bigger. +- PR diffs are more annoying (but files in `vendor/` are [hidden by default](https://github.com/github/linguist/blob/v5.2.0/lib/linguist/generated.rb#L328) on Github). ## How do I roll releases that `dep` will be able to use?