Sun, 17 Dec 2006 10:52:47 +0100 Throw out demandimport -- at least temporarily updatehook
Christian Ebert <blacktrash@gmx.net> [Sun, 17 Dec 2006 10:52:47 +0100] rev 24
Throw out demandimport -- at least temporarily
Sun, 17 Dec 2006 10:16:16 +0100 Double check encode filtered filenames updatehook
Christian Ebert <blacktrash@gmx.net> [Sun, 17 Dec 2006 10:16:16 +0100] rev 23
Double check encode filtered filenames
Sat, 16 Dec 2006 15:55:11 +0100 Added tag universal_scheme for changeset 536c1797202d updatehook
Christian Ebert <blacktrash@gmx.net> [Sat, 16 Dec 2006 15:55:11 +0100] rev 22
Added tag universal_scheme for changeset 536c1797202d
Sat, 16 Dec 2006 15:53:45 +0100 Implement $Hg$ scheme with update hook updatehook
Christian Ebert <blacktrash@gmx.net> [Sat, 16 Dec 2006 15:53:45 +0100] rev 21
Implement $Hg$ scheme with update hook The pivotal line for update hook is: repo.dirstate.update(kwupdates, 'n') This forces hg to consider the freshly written files as not modified. Thanks to wfile(), this keeps executable bits etc. Still needs more testing. No need to check for basename/filename in keyword trigger. update hook does not need re. TODO: Walk back in history, if last change of file didn't happen in 1 of the provided changesets (update/merge?)?
Sat, 16 Dec 2006 15:42:27 +0100 Simplify for $Hg$ expansion scheme updatehook
Christian Ebert <blacktrash@gmx.net> [Sat, 16 Dec 2006 15:42:27 +0100] rev 20
Simplify for $Hg$ expansion scheme
Sat, 16 Dec 2006 15:38:25 +0100 Use the "parent1|2" kwargs to detect file state updatehook
Christian Ebert <blacktrash@gmx.net> [Sat, 16 Dec 2006 15:38:25 +0100] rev 19
Use the "parent1|2" kwargs to detect file state Can parent2 be of further use? Like in parsing back history? Adapt keyword trigger to $Hg$ scheme.
Sat, 16 Dec 2006 15:28:42 +0100 Simplify filter pattern for $Hg$ scheme updatehook
Christian Ebert <blacktrash@gmx.net> [Sat, 16 Dec 2006 15:28:42 +0100] rev 18
Simplify filter pattern for $Hg$ scheme Adapt keyword trigger as well.
(0) -10 -7 +7 +10 +30 +100 +300 +1000 tip