unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: git and changelogs
Date: Tue, 15 Jul 2008 19:28:02 +0100	[thread overview]
Message-ID: <49dd78620807151128h2d9a87fbi6ea26dac45aa2f59@mail.gmail.com> (raw)
In-Reply-To: <87prpfgguz.fsf@gnu.org>

2008/7/15 Ludovic Courtès <ludo@gnu.org>:
> Hello!
>
> "Neil Jerram" <neiljerram@googlemail.com> writes:
>>
>> Attached is my attempt (thus far) at such a program.  Comments
>> welcome, of course.
>
> IIUC, the idea is to fill in `ChangeLog' files as usual and then let
> this program extract entries from there and put them in the Git log,
> right?

Yes.

>  That seems useful, but it means you can't use your favorite
> front-end to commit.

Yes, that is a problem.

>> It would be good if we could reach a clear
>> decision on whether to abolish ChangeLogs, or not!
>
> I'd say "yes", but OTOH, I haven't found anything like Emacs'
> `add-change-log-entry' that would fit nicely into my workflow (I did
> look at DVC but it looks unmaintained and undocumented ATM).  IOW,
> laziness has won so far.  :-)

Agreed.  It is important to get a good workflow, and with the program
that I attached, it is inelegant that it does the "git commit" itself,
because it takes away flexibility in what args one might pass to "git
commit".

So more work is needed...  I wonder if adding code into one of Git's
hook might work?

Also I met Alfred Szmidt at the GNU hackers meeting in Bristol, and he
was working on a solution for Emacs - but I think that assumes doing
the commit from Emacs.

> Thanks,
> Ludo'.

Thanks for your thoughts!

      Neil




  reply	other threads:[~2008-07-15 18:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 15:38 git and changelogs Andy Wingo
2008-05-09 20:08 ` Ludovic Courtès
2008-05-17 20:53   ` Han-Wen Nienhuys
2008-05-09 22:41 ` Neil Jerram
2008-05-11  3:09   ` Ludovic Courtès
2008-05-12 19:10   ` Andy Wingo
2008-05-12 20:12     ` Neil Jerram
2008-05-12 21:35       ` Andy Wingo
2008-05-22 21:02 ` Thien-Thi Nguyen
2008-07-11 22:22   ` Neil Jerram
2008-07-15 18:08     ` Ludovic Courtès
2008-07-15 18:28       ` Neil Jerram [this message]
2008-07-15 18:54     ` Ludovic Courtès
2008-07-16 21:51     ` Ludovic Courtès
2008-07-17 21:24       ` Neil Jerram
2008-07-17 21:29         ` Neil Jerram
2008-07-18 13:05         ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49dd78620807151128h2d9a87fbi6ea26dac45aa2f59@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).