From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: RFD: please drop ChangeLog updates
Date: Fri, 29 Aug 2008 17:32:55 -0700 [thread overview]
Message-ID: <m3bpzbtk94.fsf@pobox.com> (raw)
In-Reply-To: <87zlmvfvcv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 29 Aug 2008 21:56:48 +0200")
Hi,
On Fri 29 Aug 2008 12:56, ludo@gnu.org (Ludovic Courtès) writes:
> That said, the ideal would be something like `add-change-log-entry' that
> operates on Git logs instead of ChangeLogs, but there doesn't seem to be
> anything like this. DVC is said to support things like that, but it
> doesn't seem to be well documented.
C-x V a I think.
I wrote about DVC here:
http://wingolog.org/archives/2008/03/11/using-newfangled-version-control-systems-from-emacs
My work flow goes like this:
* hack hack hack
* M-x dvc-diff
* j to go back and forth between file list and diffs
* t to add a log entry
* in the log entry, C-c C-c to commit
* in the diff buffer, g to refresh
That's about it, and works really well for me.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-08-30 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:30 RFD: please drop ChangeLog updates dsmich
2008-08-29 2:47 ` Han-Wen Nienhuys
2008-08-29 9:46 ` Sergey Poznyakoff
2008-08-29 19:56 ` Ludovic Courtès
2008-08-29 23:47 ` Han-Wen Nienhuys
2008-08-30 18:40 ` Ludovic Courtès
2008-08-30 19:11 ` Han-Wen Nienhuys
2008-08-30 19:31 ` Ludovic Courtès
2008-08-30 21:11 ` Neil Jerram
2008-08-31 10:30 ` Ludovic Courtès
2008-08-30 0:32 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 14:40 Han-Wen Nienhuys
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=m3bpzbtk94.fsf@pobox.com \
--to=wingo@pobox.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).