| commit | 30dd44e7197a10f768dfeb22b67c767fda24a5d4 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 19 Apr 2008 02:32:33 +0000 (18 22:32 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 11 May 2008 05:16:34 +0000 (11 01:16 -0400) | ||
| tree | 1960413f51fd592cb868a25a8d157205b594dad2 | treesnapshot (tar.gz zip) |
| parent | 708b180920047af3dbb569e2c20ead0e5cfed6d5 | commitdiff |
Remove unused RemoteSpec now that RemoteConfig, RefSpec superseded it
The RemoteSpec class had good intentions of handling the remote
configuration data necessary for a fetch or push operation, but
wasn't quite abstracted out in a way that would lead to good reuse,
nor is it actually used by the existing fetch implementation.
Now that RemoteConfig and RefSpec accurately model the remote
block of a config file we won't be needing this first draft
attempt anymore.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
The RemoteSpec class had good intentions of handling the remote
configuration data necessary for a fetch or push operation, but
wasn't quite abstracted out in a way that would lead to good reuse,
nor is it actually used by the existing fetch implementation.
Now that RemoteConfig and RefSpec accurately model the remote
block of a config file we won't be needing this first draft
attempt anymore.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>