On Mon, Mar 30, 2009 at 01:59:09PM -0300, Devan Goodwin wrote:
>
> 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?
Yes, I'd appreciate one email per commit.
--
Rob James wrote:
Just been running through the install process from scratch for
Spacewalk 0.5 and the certificate generation which the docs say is
nessecery seems to be quite a pain. Can gen-oss-sat-cert.pl and
template-eval.cert at least be included (maybe in spacewalk-admin) to
make things a li
Just been running through the install process from scratch for
Spacewalk 0.5 and the certificate generation which the docs say is
nessecery seems to be quite a pain. Can gen-oss-sat-cert.pl and
template-eval.cert at least be included (maybe in spacewalk-admin) to
make things a little easier? Even b
Jesus Rodriguez wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 01 Apr 2009 11:08:52 +0200
Miroslav Suchý wrote:
> Jesus M. Rodriguez wrote:
> > EEK, build-missing*.sh should use tito to be consistent with
> > the rest of the builds we've been doing. Can we please fix that?
>
> And do we have build.py.pr
Jesus M. Rodriguez wrote:
EEK, build-missing*.sh should use tito to be consistent with
the rest of the builds we've been doing. Can we please fix that?
And do we have build.py.props in every package dir? No.
The problem is that we have in some dirs only Makefile and in some dirs
only build.py
Jesus M. Rodriguez wrote:
We still use that script? I didn't think anyone used that, we probably
need to see if it still works (besides the recent untagging).
Yes, it build packages for nightly repo.
--
Miroslav Suchy
RHN Satellite Engineering, Red Hat
