On Thu, Mar 26, 2009 at 9:24 AM, Jason Dobies wrote:
>> Problem we have is some of the commit logs are very wordy (which is ok
>> but the first sentence isn't descriptive enough) and others are
>> so terse that I don't bother including them: fixed unit test.
>
> Would it be valuable to preface tr
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Mar 2009 09:24:28 -0400
Jason Dobies wrote:
Problem we have is some of the commit logs are very wordy (which is
ok but the first sentence isn't descriptive enough) and others are
so terse that I don't bother includ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Mar 2009 09:24:28 -0400
Jason Dobies wrote:
> > Problem we have is some of the commit logs are very wordy (which is
> > ok but the first sentence isn't descriptive enough) and others are
> > so terse that I don't bother including them: fi
Problem we have is some of the commit logs are very wordy (which is ok
but the first sentence isn't descriptive enough) and others are
so terse that I don't bother including them: fixed unit test.
Would it be valuable to preface trivial commit messages with something
so they can be filtered ou
On Wed, Mar 25, 2009 at 09:13:13PM -0400, James Bowes wrote:
> If tito doesn't find a changelog entry in the specfile during a tag
> operation, he can now create one himself from the git logs. The entry
> line items are made from the subject and email of committer for all
> untagged commits of the
If tito doesn't find a changelog entry in the specfile during a tag
operation, he can now create one himself from the git logs. The entry
line items are made from the subject and email of committer for all
untagged commits of the package in question.
If you don't like tito doing your work for you,
