starting to use ditrack - dev roadmap

[Luke Kenneth Casson Leighton]

> > _after_ a commit, _then_ a nice unique ordered numbering
> > could be applied.
>
> Current numbering scheme has disadvantages but it's simple and may be used
> 'inline' in mail, chat, etc... I think You won't write to somebody
>
> "I've closed issue #c675522f-76ef-47a1-bb24-107ea83534eb" :)

 precisely - that's why, _after_ a commit, the nice unique numbering
 is applied.  i've looked at the code a bit more closely, now: for comments,
 a "local" numbering scheme is applied (with letters not numbers) then
 after commit, this is turned into a "real" numbering scheme.

> > basically, ditrack as it stands is perfect for a single user,

> I tried to use ditrack with git but problems with numbering You'd
> mentioned above make this hybrid unusable.

 oo, how far did you get? send me what you have i'll see if i can
 munge it a bit, later - i am pushed for time to get this email interface
 going (on svn) first priority.

> P.S I'm not ditrack developer or expert or even advanced
> user :)

 pffh, who is? :)  sooooon become one, when you neeed something baad ha ha