| commit | 2ffea2e6cb1e1ae271871dfbda32cc9949dfa96f | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 13 Mar 2006 08:22:58 +0000 (13 03:22 -0500) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 13 Mar 2006 08:22:58 +0000 (13 03:22 -0500) | ||
| tree | c4e04106055d2c06e3f0c1f8de79e75d1305973a | treesnapshot (tar.gz zip) |
| parent | eb6ade9ebdb705f48eb421738745a3d070c5783f | commitdiff |
Reworked the provider connection logic so that we can
properly catch failures from the implementation and report
them in the UI. Unfortunately the Eclipse method of doing
this is just outright difficult to write. Who ever thought
that handling an error would require so much work on the
part of the developer writing a simple wizard?
If we can't find a .git directly in the top level of the
project directory then we create it during a connection;
otherwise we use the existing .git directory. This is
clearly not ideal as we should allow searching for a .git
directory in a parent or a .git directory within a single
folder within the project. But I'm not sure I would agree
with allowing multiple .git directories within a single
project but in different folders of that project.
Patch: Prototype-Implementation
properly catch failures from the implementation and report
them in the UI. Unfortunately the Eclipse method of doing
this is just outright difficult to write. Who ever thought
that handling an error would require so much work on the
part of the developer writing a simple wizard?
If we can't find a .git directly in the top level of the
project directory then we create it during a connection;
otherwise we use the existing .git directory. This is
clearly not ideal as we should allow searching for a .git
directory in a parent or a .git directory within a single
folder within the project. But I'm not sure I would agree
with allowing multiple .git directories within a single
project but in different folders of that project.
Patch: Prototype-Implementation