Revert of Add --no-history option to fetch and gclient for shallow clones.

Revert of Add --no-history option to fetch and gclient for shallow clones. (https://codereview.chromium.org/437903002/)

Reason for revert:
Broke the WebRTC waterfall:
http://build.chromium.org/p/tryserver.webrtc/builders/win/builds/3958/steps/gclient%20revert/logs/stdio

Original issue's description:
> Add --no-history option to fetch and gclient for shallow clones.
> 
> Many people* have complained on chromium-dev about the long times
> required to perform a full fetch over a DSL. This seems to be mostly
> due to the huge size of chromium's history (~9 GB). On the other side,
> not everybody is interested in downloading the full git history of
> the projects. The size of git packs required to fetch a working HEAD
> is one order of magnitude smaller (1.5 GB).
> This change makes it possible to perform a shallow fetch (in a way
> which is consistent with DEPS, leveraging git templates on clone),
> reducing fetch times by 80% for those not interested in the history.
> 
> * See: 
> [chromium-dev] "fetch chromium" keeps hanging/getting stuck on Windows 7
> [chromium-dev] Initial checkout with git taking long
> [chromium-dev] Trying to get latest source code fails when fetching
> [chromium-dev] Gclient sync takes too long
> 
> BUG=228996
> 
> Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=287606

TBR=iannucci@chromium.org,szager@chromium.org,wtc@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=228996
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=287637

[Primiano Tucci (use gerrit), 2014-08-05 23:14:48]

Created Revert of Add --no-history option to fetch and gclient for shallow
clones.

[Primiano Tucci (use gerrit), 2014-08-05 23:15:57]

More details about the breakage:

Traceback (most recent call last):
  File "E:\b\depot_tools\\gclient.py", line 2067, in <module>
    sys.exit(Main(sys.argv[1:]))
  File "E:\b\depot_tools\\gclient.py", line 2055, in Main
    return dispatcher.execute(OptionParser(), argv)
  File "E:\b\depot_tools\subcommand.py", line 245, in execute
    return command(parser, args[1:])
  File "E:\b\depot_tools\\gclient.py", line 1891, in CMDrevert
    return client.RunOnDeps('revert', args)
  File "E:\b\depot_tools\\gclient.py", line 1342, in RunOnDeps
    work_queue.flush(revision_overrides, command, args, options=self._options)
  File "E:\b\depot_tools\gclient_utils.py", line 859, in flush
    self._run_one_task(self.queued.pop(i), args, kwargs)
  File "E:\b\depot_tools\gclient_utils.py", line 951, in _run_one_task
    task_item.run(*args, **kwargs)
  File "E:\b\depot_tools\\gclient.py", line 744, in run
    file_list)
  File "E:\b\depot_tools\gclient_scm.py", line 160, in RunCommand
    return getattr(self, command)(options, args, file_list)
  File "E:\b\depot_tools\gclient_scm.py", line 656, in revert
    return self.update(options, [], file_list)
  File "E:\b\depot_tools\gclient_scm.py", line 389, in update
    self._Clone(revision, url, options)
  File "E:\b\depot_tools\gclient_scm.py", line 830, in _Clone
Sending crash report ...
  args: ['E:\\b\\depot_tools\\\\gclient.py', 'revert', '-v', '-v', '-v',
'--nohooks', '--upstream']
  cwd: E:\b\build\slave\win\build
  exception: Values instance has no attribute 'no_history'
  host: VM207-M4.golo.chromium.org
  stack:   File "E:\b\depot_tools\\gclient.py", line 2067, 
  user: chrome-bot
  version: 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500
    if options.no_history:
AttributeError: Values instance has no attribute 'no_history'
A stack trace has been sent to the maintainers.

[Primiano Tucci (use gerrit), 2014-08-05 23:16:17]

The CQ bit was checked by primiano@chromium.org

[commit-bot: I haz the power, 2014-08-05 23:16:52]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/primiano@chromium.org/440263002/1

[commit-bot: I haz the power, 2014-08-05 23:19:31]

Change committed as 287637

[iannucci, 2014-08-06 18:44:51]

On 2014/08/05 23:19:31, I haz the power (commit-bot) wrote:
> Change committed as 287637

Aww... I was going to recommend filling in options.no_history at the point where
we parse the option. The problem with this approach is that it can lead to
copy-pasta, and suddenly we have 2 (or 3, or 4) places where 'False' is a local,
implied default. Then someone gets clever and changes the local default to True
in one of the places, and we have chaos :(

[Primiano Tucci (use gerrit), 2014-08-06 19:07:16]

On 2014/08/06 18:44:51, iannucci wrote:
> On 2014/08/05 23:19:31, I haz the power (commit-bot) wrote:
> > Change committed as 287637
> 
> Aww... I was going to recommend filling in options.no_history at the point
where
> we parse the option. The problem with this approach is that it can lead to
> copy-pasta, and suddenly we have 2 (or 3, or 4) places where 'False' is a
local,
> implied default. Then someone gets clever and changes the local default to
True
> in one of the places, and we have chaos :(

Robert and I had an offline chat on this. The point is that even filling the
options is not going to solve the problem (if the default changes, we need to
change all the = False filling assignments).
On the other side, there seem to be already precedent for this
(with_branch_heads), so we decided to stay consistent. Also, at current state,
there is only one place evaluating no_history and, honestly, I wouldn't expect
more.