* shell commands in ReleaseNotes
@ 2009-09-19 21:57 Resul Cetin
2009-09-19 22:30 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Resul Cetin @ 2009-09-19 21:57 UTC (permalink / raw)
To: git
Hi,
I noticed that there are small part of commands at the end of a not yet
released ReleaseNote-*.txt.
---
exec >/var/tmp/1
O=v1.6.4.1-266-g235db15
echo O=$(git describe master)
git shortlog --no-merges $O..master --not maint
As far as I understand it means that the output is redirected to /var/tmp/1.
Then there is O set to the last it which was used to generate a shortlog.
Then the current desciption (tag+suffix) is printed which can then used to
replace the O= line in the small snipped. Then there will be created a
shortlog from the last point it was created until master without stuff in
maint (or reachable by maint? I am not sure about that one).
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? My current idea
would be: Open the editor an copy the snipped. Open a terminal, switch to the
repository and go paste the snipped into it. After that the terminal has to be
closed as it isn't really useful anymore. An extra editor will be used to open
/var/tmp/1 and now the first step is to replace "O=v1.6.4.1-266-g235db15" with
a new id at the first line in /var/tmp/1. Now the maintainer has to order all
commits a little bit and write the release notes. After he finished it, he
just commits it to master and is finished for this period of time.
Is this real how it is done in git.git or is there maybe something I don't see
right now?
Best regards,
Resul Cetin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: shell commands in ReleaseNotes
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
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2009-09-19 22:30 UTC (permalink / raw)
To: Resul Cetin; +Cc: git
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: shell commands in ReleaseNotes
2009-09-19 22:30 ` Junio C Hamano
@ 2009-09-19 22:40 ` Resul Cetin
0 siblings, 0 replies; 3+ messages in thread
From: Resul Cetin @ 2009-09-19 22:40 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-09-19 22:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).