GNU Thales - Tasks: task #3030, Keep track of nick changes
You are not allowed to post comments on this tracker with your current authentication level.
task #3030: Keep track of nick changes
Submitter: | Lucas Nussbaum <lnu> | ||
Submitted: | Sat 10 Jan 2004 11:28:21 PM UTC | ||
Category: | Thales | Should Start On: | Sat 10 Jan 2004 12:00:00 AM UTC |
Should be Finished on: | Sat 31 Jan 2004 12:00:00 AM UTC | Priority: | 1 - Later |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
Fri 16 Jan 2004 10:07:15 PM UTC, comment #1: |
Lucas Nussbaum <lnu> |
Sat 10 Jan 2004 11:28:21 PM UTC, original submission:
|
Lucas Nussbaum <lnu> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-01-16 | lnu | Category | Thales documentation | Thales | |
Priority | 5 - Normal | 1 - Later |
Powered by Savane 3.13-d3ae.
Corresponding source code
I'm still looking for a clean way to implement this. Is something working like an history is really needed ? I'm not sure.