Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Git commit methodology
Date: Tue, 31 Aug 2010 13:47:51 -0500	[thread overview]
Message-ID: <87zkw21uw8.fsf@lifelogs.com> (raw)
In-Reply-To: <m31v9gt6sn.fsf@quimbies.gnus.org>

On Mon, 30 Aug 2010 18:16:24 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I don't think anyone has done work on this but it does sound useful.

LMI> Actually, `C-c C-a' in the vc log buffer does some of this.  It pulls in
LMI> the ChangeLog texts, but it doesn't really massage them into git/bzr
LMI> format. 

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?

Ted




  parent reply	other threads:[~2010-08-31 18:47 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 [this message]
2010-08-31 18:51           ` Lars Magne Ingebrigtsen
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=87zkw21uw8.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).