From: Gary Thomas <gary@chez-thomas.org>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>,
eCos patches <ecos-patches@sources.redhat.com>
Subject: Re: Welcome to sources.redhat.com
Date: Tue, 06 Aug 2002 12:41:00 -0000 [thread overview]
Message-ID: <1028662896.17057.146.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3D502478.3060807@ecoscentric.com>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On Tue, 2002-08-06 at 13:33, Jonathan Larmour wrote:
> Gary Thomas wrote:
> > On Tue, 2002-08-06 at 13:17, Jonathan Larmour wrote:
> >
> >
> >>Gary takes the former approach I believe, although perhaps he has emacs
> >>macros or something to help him which might be why.
> >>
> >>Commit log messages are also important as they are what people see in the
> >>ecos-cvs list, which I certainly read, and I'm pretty sure Gary does too.
> >>Yeah, what fun lives we lead ;).
> >
> >
> > I *do* have emacs macros which help with this.
>
> Okay, can you indulge me with a peek? :-).
>
Here's what I have in my .emacs file:
(require 'add-log)
(global-set-key "\C-x4a" 'add-change-log-entry)
;; (defun user-mail-address () "gthomas@redhat.com")
(defun user-mail-address () "gary@chez-thomas.org")
(defun user-full-name () "Gary Thomas")
Then, to make a ChangeLog entry, I just go to the file/function where
the change was made, type ^X-4-a and it finds the appropriate ChangeLog
file, makes the basic entry and I just fill in the details.
What I normally do is to run a script to see what I've changed
(cvs-patch), then run another script which runs emacs on all of the
changed files so I can update the ChangeLog (do_ChangeLogs). Then run
the (cvs-patch) script one more time and commit.
[-- Attachment #2: cvs-patch --]
[-- Type: text/x-sh, Size: 150 bytes --]
#! /bin/sh
#cvs -q diff $* | FixPatch | tee /work/diffs
#cvs -q diff $* | FixPatch | no_srec >/work/diffs
cvs -q diff $* | no_srec >/work/diffs
[-- Attachment #3: do_ChangeLogs --]
[-- Type: text/x-sh, Size: 222 bytes --]
#! /bin/sh
#grep Index $1 | sed -e "s/Index: //" | xargs -n1 xemacs $1
grep Index: /work/diffs | grep -v "%redact" | grep -v ChangeLog | grep -v .Sanitize | sed -e "s/Index: //" | xargs -n1 ${CVSEDITOR} /work/diffs
next prev parent reply other threads:[~2002-08-06 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020806155646.18120.qmail@sources.redhat.com>
2002-08-06 11:07 ` Jonathan Larmour
2002-08-06 11:55 ` Andrew Lunn
2002-08-06 12:12 ` Gary Thomas
2002-08-06 12:17 ` Jonathan Larmour
2002-08-06 12:24 ` Gary Thomas
2002-08-06 12:33 ` Jonathan Larmour
2002-08-06 12:41 ` Gary Thomas [this message]
2002-08-06 14:53 ` Jonathan Larmour
2002-08-07 1:13 ` Andrew Lunn
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=1028662896.17057.146.camel@hermes.chez-thomas.org \
--to=gary@chez-thomas.org \
--cc=ecos-maintainers@sources.redhat.com \
--cc=ecos-patches@sources.redhat.com \
--cc=jifl@ecoscentric.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).