-
```
Log4j has awesome formatting feature, why not log4go? The formatting in log4go
is really strict, for instance, I don't want to see the timezone but I want to
see the second and millisecond info,…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It would be better if the source code were into a directory with a name ready
to import.
So, instead of:
import l4g "log4go.googlecode.com/svn/stable"
we could use it directly from:
i…
-
```
It's currently impossible to maintain references to log4go level values outside
the package.
For example, I want to have the log level configurable through a flag. To do
this I map a symbolic n…
-
```
It's currently impossible to maintain references to log4go level values outside
the package.
For example, I want to have the log level configurable through a flag. To do
this I map a symbolic n…