From: Resul Cetin <Resul-Cetin@gmx.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: shell commands in ReleaseNotes
Date: Sun, 20 Sep 2009 00:40:49 +0200 [thread overview]
Message-ID: <200909200040.50009.Resul-Cetin@gmx.net> (raw)
In-Reply-To: <7veiq27ekz.fsf@alter.siamese.dyndns.org>
> Resul Cetin <Resul-Cetin@gmx.net> writes:
> > Real nice idea to create an overview about changes in a repository for
> > writing a releasenotes. But how is it real used by the maintainer?
>
> Open the file, go to the beginning of the scriptlet and mark (\C-SP), go
> to the end (\M->), feed it to shell (\M-| sh RET), open /var/tmp/1 and
> read it over while cutting the updated definition of O=.
>
> Everything done in Emacs, no need for any extra editor.
Ah, thanks. Looks like a good workflow.
prev parent reply other threads:[~2009-09-19 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 21:57 shell commands in ReleaseNotes Resul Cetin
2009-09-19 22:30 ` Junio C Hamano
2009-09-19 22:40 ` Resul Cetin [this message]
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=200909200040.50009.Resul-Cetin@gmx.net \
--to=resul-cetin@gmx.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).