unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: Dan Nicolaescu <dann@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: How to get commit message on vc-change-log
Date: Fri, 30 Jul 2010 12:29:18 +0530	[thread overview]
Message-ID: <m3y6ct5ubd.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <yxq1vanv1e2.fsf@fencepost.gnu.org>

On Wed, 28 Jul 2010 15:42:45 -0400, Dan Nicolaescu <dann@gnu.org> wrote:
> "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com> writes:
> 
> > On Wed, 28 Jul 2010 04:16:45 -0400, Dan Nicolaescu <dann@gnu.org> wrote:
> >> aneesh.kumar@linux.vnet.ibm.com (Aneesh Kumar K.V) writes:
> >> 
> >> > Hi,
> >> >
> >> > What command will help me find the the commit message 
> >> > of a commit in logview ?. 'D' gives me diff but not the commit message
> >> 
> >> Are you looking from the short format log (like the one from C-x v L)
> >> and you want to see the full commit message, not just the one line
> >> form?
> >
> > full commit message
> >
> >> 
> >> It sounds like a good idea that we should provide a command to show
> >> the full log.
> >
> > I was expecting to get the output of 'git show'  with 'D' key. 
> 
> D shows just the diff.  This is the fist time that someone requests to
> see the log too...
> 
> IMO we need more input from git users about what's better here: 
> use git show for D, leave it as it is and add another command for git
> show, etc.
> 

I have already filed bugs related to these against emacs. I will
continue to do so and can help in vc-git.el testing.

-aneesh



      reply	other threads:[~2010-07-30  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  6:13 How to get commit message on vc-change-log Aneesh Kumar K.V
2010-07-28  6:20 ` Óscar Fuentes
2010-07-28  8:16 ` Dan Nicolaescu
2010-07-28  9:09   ` Aneesh Kumar K. V
2010-07-28 19:42     ` Dan Nicolaescu
2010-07-30  6:59       ` Aneesh Kumar K. V [this message]

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/emacs/

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

  git send-email \
    --in-reply-to=m3y6ct5ubd.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=dann@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).