-
Notifications
You must be signed in to change notification settings - Fork 0
/
sample.log
75 lines (54 loc) · 1.83 KB
/
sample.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
## -*- work-log -*-
##
## * entry was completed on that day
## + entry was completed on a later day
## - entry was decided against on a later day
##
## > When I accomplish something, I write a * line that day.
## >
## > Whenever a bug / missing feature is mentioned during the day and I
## > don't fix it, I make a note of it. Some things get noted many times
## > before they get fixed.
## >
## > Occasionally I go back through the old notes and mark with a + the
## > things I have since fixed.
##
## SEE ALSO
## <http://doom-ed.com/blog/1997/10/10/last-two-months-of-work-log>
## <http://www.team5150.com/~andrew/carmack/plan.html>
## ---------------------------------------------------------------------
2009-05-02
advertise work-log.el (ru_emacs, emacs?)
repair Vostro's keyboard
2009-04-10
cannot save hpOV attachments
- list of call transaction types (Re: WRK-126200)
2009-04-09
+ hack "log-mode": start with implementing `C-x 4 a' (change-log-mode)
+ fix jabber-el's "Idle" status
2009-04-07
finish processUssd2.in
implement "w4" macros for TOC sections
* new processSdp
2009-03-10
+ qemu.sh fails (Could not initialize device 'tap') {
modprobe tun
udevadm settle
ifup tap0
}
+ shrink recdump field #9 (64 characters max)
- "Farewell to Ekotel!" preprocessing changes
2009-03-04
* ask for updated SDP CDR specification
* explain FORIS people how to distinguish USSD2 events in SDP CDRs
+ [processSdp] update field #9 of SDP recdump
- edit plain text Google docs in Emacs ==> one and only LOG file
- patch `ghostscript' package (configurable `-sPAPERSIZE')
2009-03-02
* mysql with cyrillic letters {
LANG=ru_RU.cp1251 mysql
screen> :encoding cp1251
}
* make Bugzilla (BZ) accessible via Apache
+ create a bug in BZ web UI, adding self to `CC'
+ receive email from BZ