bugseverywhere - Bugtracker built on distributed version control

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fixed libbe.command.diff + ugly BugDir.duplicate_bugdir implementation	W. Trevor King	2009-12-15	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	duplicate_bugdir() works, but for the vcs backends, it could require shelling out for _every_ file read. This could, and probably will, be horribly slow. Still it works ;). I'm not sure what a better implementation would be. The old implementation checked out the entire earlier state into a temporary directory pros: single shell out, simple upgrade implementation cons: wouldn't work well for HTTP backens I think a good solution would run along the lines of the currently commented out code in duplicate_bugdir(), where a VersionedStorage.changed_since(revision) call would give you a list of changed files. diff could work off of that directly, without the need to generate a whole duplicate bugdir. I'm stuck on how to handle upgrades though... Also removed trailing whitespace from all python files.
*	Fixed libbe.command.subscribe	W. Trevor King	2009-12-15	1	-10/+11
\|
*	Transition to Command-format complete.	W. Trevor King	2009-12-15	1	-4/+4
\| \| \| \| \| \| \| \|	Well, except for going through and updating the _long_help() strings. $ python test.py libbe.command succeeds for everything except Diff and Subscribe, which is expected since I haven't fixed up libbe.diff yet.
*	Transitioned diff and subscribe to Command-format"	W. Trevor King	2009-12-15	1	-135/+157
\| \| \| \| \| \|	They don't work yet, since I still need to fix up libbe.diff and replace BugDir.duplicate_bugdir() with something based on the new Storage backend.
*	Initial directory restructuring to clarify dependencies	W. Trevor King	2009-12-07	1	-0/+360