From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Git commit methodology
Date: Tue, 31 Aug 2010 20:51:37 +0200 [thread overview]
Message-ID: <m3iq2qty2u.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87zkw21uw8.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> It's really "Gnus commit" format. It's sort of becoming standard (Emacs
> has a similar format) but there's no requirement to use it in Gnus
> commits, just my gentle nudges. So I don't know if it needs to be
> codified. Do you have a preference? Looking at `git log --oneline' do
> you see a better way?
I think the format you describe makes a lot of sense. So it'd be nice
if `C-c C-a' codified it.
And `C-c C-a' pulls in changes to files that aren't going to be
committed, so it's kinda not optimal. It should be fixed. By
somebody. :-)
I mean, when I'm doing development, the commits just kinda spurt out.
Having to spend a second more than necessary on the vc formalities is a
downer, so Emacs should just get this right...
I'll probably take a whack at hacking `C-c C-a' to DWIM.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-08-31 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 14:41 Lars Magne Ingebrigtsen
2010-08-30 13:31 ` Ted Zlatanov
2010-08-30 13:38 ` Lars Magne Ingebrigtsen
2010-08-30 13:48 ` Ted Zlatanov
2010-08-30 16:16 ` Lars Magne Ingebrigtsen
2010-08-30 17:03 ` Lars Magne Ingebrigtsen
2010-08-30 17:10 ` Leo
2010-08-30 17:12 ` Lars Magne Ingebrigtsen
2010-08-30 17:18 ` Leo
2010-08-30 17:22 ` Lars Magne Ingebrigtsen
2010-08-30 17:34 ` Leo
2010-08-30 17:51 ` Lars Magne Ingebrigtsen
2010-08-30 20:16 ` Lars Magne Ingebrigtsen
2010-08-30 18:51 ` Steinar Bang
2010-08-31 18:47 ` Ted Zlatanov
2010-08-31 18:51 ` Lars Magne Ingebrigtsen [this message]
2010-09-01 13:50 ` Ted Zlatanov
2010-09-01 14:42 ` Lars Magne Ingebrigtsen
2010-09-01 15:06 ` Ted Zlatanov
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=m3iq2qty2u.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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 NNTP newsgroup(s).