Markus Rothe wrote: [Tue Aug 09 2005, 07:36:18AM EDT]
> Personaly I find it a little bit annoying to write changes twise.
> One time in Changelog and one time in --commitmsg. How about using
> the commitmsg for Changelog as default, but if a Changelog entry
> already exists, then write nothing
Ciaran McCreesh wrote:
On Tue, 09 Aug 2005 15:07:16 -0400 Jonathan Smith <[EMAIL PROTECTED]>
wrote:
| i do have one suggestion for every dev who's ever gotten minor syntax
| - trailing whitespace errors (somehow that happens to me ALOT)...
Or use vim, and :set list listchars=tab:»·,trail:·,exten
On Tue, 2005-08-09 at 20:22 +0100, Ciaran McCreesh wrote:
> Or use vim, and :set list listchars=tab:»·,trail:·,extends:… , and then
> you'll be able to see them visibly.
Or use a proper editor and do the following ;)
(global-font-lock-mode t)
(setq-default show-trailing-whitespace t)
Regards,
On Tue, 09 Aug 2005 15:07:16 -0400 Jonathan Smith <[EMAIL PROTECTED]>
wrote:
| i do have one suggestion for every dev who's ever gotten minor syntax
| - trailing whitespace errors (somehow that happens to me ALOT)...
Or use vim, and :set list listchars=tab:»·,trail:·,extends:… , and then
you'll be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> Isn't this one of those things that's best done on a per-dev basis?
> It's so trivial there's no point shipping an app that does it --
> reading the associated documentation would take longer than writing
> your own. Plus that
Ciaran McCreesh wrote:
> Isn't this one of those things that's best done on a per-dev basis?
> It's so trivial there's no point shipping an app that does it --
> reading the associated documentation would take longer than writing
> your own. Plus that way you can incorporate personalised clever thi
On Tue, 9 Aug 2005 12:23:20 + Markus Rothe <[EMAIL PROTECTED]>
wrote:
| Stephen Bennett wrote:
| > On Tue, 9 Aug 2005 11:36:18 +
| > Markus Rothe <[EMAIL PROTECTED]> wrote:
| >
| > > Personaly I find it a little bit annoying to write changes twise.
| > > One time in Changelog and one time
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 .bashr
Stephen Bennett wrote:
> On Tue, 9 Aug 2005 11:36:18 +
> Markus Rothe <[EMAIL PROTECTED]> wrote:
>
> > Personaly I find it a little bit annoying to write changes twise. One
> > time in Changelog and one time in --commitmsg. How about using the
> > commitmsg for Changelog as default, but if a C
Markus Rothe wrote:
Personaly I find it a little bit annoying to write changes twise. One
time in Changelog and one time in --commitmsg. How about using the
commitmsg for Changelog as default, but if a Changelog entry already
exists, then write nothing to Changelog.
#!/bin/bash
echangelog "${1}
On Tue, 9 Aug 2005 11:36:18 +
Markus Rothe <[EMAIL PROTECTED]> wrote:
> Personaly I find it a little bit annoying to write changes twise. One
> time in Changelog and one time in --commitmsg. How about using the
> commitmsg for Changelog as default, but if a Changelog entry already
> exists, th
Ciaran McCreesh wrote:
> If you're the sort that writes good ChangeLog messages anyway, there's
> nothing wrong with reusing them as the commit message. If you have a
> really really good reason for not using a ChangeLog message, or if you
> haven't yet written a shell alias for reusing ChangeLog m
Well, you'd think that doing main tree CVS commit messages would be
something that everyone could do properly without being told, but sadly
this doesn't seem to be the case. S...
Believe it or not, commit messages are not just something that you type
in to keep a computer happy. These messages
13 matches
Mail list logo
