From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proper commit messages
Date: Tue, 9 Aug 2005 14:40:55 +0200 [thread overview]
Message-ID: <200508091441.04339@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <42F899AE.5020600@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Tuesday 09 August 2005 13:55, Simon Stelling wrote:
> #!/bin/bash
> echangelog "${1}"
> repoman scan
> repoman commit -m "${1}"
Even simpler, as repoman commit abort in case of errors in repoman scan:
ecommit() {
echangelog "$@"
repoman commit -m "$@"
}
add that to your .bashrc.
I use it always:
ecommit "Stable on amd64"
and it's done :)
If something is bad, it stops me.
If the package is mine and I want to have it clear, repoman full before
ecommit to be safe.
--
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-09 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 20:44 [gentoo-dev] Proper commit messages Ciaran McCreesh
2005-08-09 11:36 ` Markus Rothe
2005-08-09 11:55 ` Simon Stelling
2005-08-09 12:40 ` Diego 'Flameeyes' Pettenò [this message]
2005-08-09 12:04 ` Stephen Bennett
2005-08-09 12:23 ` Markus Rothe
2005-08-09 12:47 ` Ciaran McCreesh
2005-08-09 12:59 ` Markus Rothe
2005-08-09 19:07 ` Jonathan Smith
2005-08-09 19:22 ` Ciaran McCreesh
2005-08-09 20:56 ` Henrik Brix Andersen
2005-08-09 22:54 ` Tuan Van
2005-08-09 23:31 ` [gentoo-dev] " Arnaud Launay
2005-08-09 23:38 ` LostSon
2005-08-09 23:40 ` Ciaran McCreesh
2005-08-09 23:48 ` Mike Frysinger
2005-08-10 8:03 ` Alin Nastac
2005-08-10 21:46 ` Dice R. Random
2005-08-11 16:16 ` Drake Wyrm
2005-08-09 23:47 ` Mike Frysinger
2005-08-15 14:03 ` [gentoo-dev] " Aron Griffis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508091441.04339@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox