Yes, Mike is exactly right here.
The only reason to wrap a log.debug() in log4j is when passing the argument(s) is very
expensive and a simple (2) string concatenation doesn't qualify. Even passing an object
with an expensive toString() argument isn't a problem because the log4j lib is
On Wednesday 25 March 2009 17:00:37 Devan Goodwin wrote:
dgilmore fixed up our jabber configs to work on 2.2 yesterday, so
updated spacewalk-config and spacewalk-setup packages correct this, but
you probably need to be on a fresh system before it will work. (i.e.
not a system where you tried
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Mar 2009 19:19:17 -0500
Dennis Gilmore den...@ausil.us wrote:
would anyone object to me creating a
spacewalk-comm...@lists.fedorahosted.org and having all commits
pushed to fedorahosted emailed there?
Dennis
Hypothetically if we could figure out a way to get it down to one
email per commit, with the subject being the *first* line of the commit
message, would people be in favor of this?
I would be, it'd read better and be a good mix of RSS and e-mail.
--
Jason Dobies
RHN Satellite / Spacewalk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cliff wrote:
Brad Buckingham wrote:
Folks,
I'd like to get your opinion
I'm currently working on a Python script that uses Spacewalk XMLRPC
APIs to list/delete system snapshots. Since this script uses the
XMLRPC APIs, it is not required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pradeep Kilambi wrote:
Brandon Perkins wrote:
Cliff wrote:
Brad Buckingham wrote:
Folks,
I'd like to get your opinion
I'm currently working on a Python script that uses Spacewalk XMLRPC
APIs to list/delete system snapshots.
Today we have two commit formats. If you are fixing a bug the format
is:
bznumber - msg
If it is not a bug fix, it is just:
msg
This has been working out ok so far. But we're getting more descriptive
in our commits which is good for looking back at history but sucks for
changelogs and 'git
