And all others packages have been untagged.
Which effectively broken down rel-eng/build-missing-builds-in-koji.sh
script.
May I propose to create 0.6 tags and/or not move the tags, but only copy
them?
Thx
--
Miroslav Suchy
RHN Satellite Engineering, Red Hat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 30 Mar 2009 22:37:12 -0400
Jesus Rodriguez jes...@redhat.com 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
On Tuesday 31 March 2009 03:11:29 am Miroslav Suchý wrote:
And all others packages have been untagged.
Which effectively broken down rel-eng/build-missing-builds-in-koji.sh
script.
May I propose to create 0.6 tags and/or not move the tags, but only copy
them?
Thx
build missing packages
On Tue, Mar 31, 2009 at 09:50:26AM +0200, Jan Pazdziora wrote:
On Mon, Mar 30, 2009 at 10:37:12PM -0400, Jesus Rodriguez wrote:
Thoughts? I suspect the lengths will cause folks to balk at this
suggestion :)
-1.
I do not like restricting length of the first line of the commit
message
Great Work on the new release guys!
Travis Camechis
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2009 11:50 AM, Jesus M. Rodriguez wrote:
Miroslav Such wrote:
And all others packages have been untagged.
Which effectively broken down rel-eng/build-missing-builds-in-koji.sh
script.
May I propose to create 0.6
[snip]
The 50 characters was a suggestion :) I could live with a oneline
summary then longer messages separated by a blank line.
My biggest fear with the 50 character limit was 'fixed bug' type
of commit messages.
I like the summary and then extended detail separation... add in IDEs in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 31 Mar 2009 13:35:17 -0400
Jesus M. Rodriguez jes...@redhat.com wrote:
Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2009 11:50 AM, Jesus M. Rodriguez wrote:
Miroslav Such wrote:
And all others
Partha Aji wrote:
Just an observation here.. I generally prefer using git ci-m message
vs using an editor.. But if we have git commit format regulations I
guess I'll have to use vi.. Would be nice though if I could stick to -m...
I really like using '-m' as well, but you can do multi-line
