Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	git@vger.kernel.org
Subject: Re: feature request: git-log should accept sth like v2.6.26-rc8-227
Date: Fri, 11 Jul 2008 00:24:28 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807110022510.3279@eeepc-johanness> (raw)
In-Reply-To: <7v8ww9pkv8.fsf@gitster.siamese.dyndns.org>

Hi,

On Thu, 10 Jul 2008, Junio C Hamano wrote:

> Jakub Narebski <jnareb@gmail.com> writes:
> 
> > Besides, it would be nice to have some command (git-rev-parse 
> > perhaps?) which could take ambiguous commit-ish, and list all commit 
> > which matches it.
> 
> Have fun writing it and send in a patch.

Note that this really could be a patch, but not for rev-parse.  Patch 
revision.c instead to parse the argument into _all_ matching revisions.

The :/ notation I no longer like so much should give you a lot of 
inspiration.

Good luck,
Dscho

  reply	other threads:[~2008-07-10 22:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 18:57 feature request: git-log should accept sth like v2.6.26-rc8-227 Toralf Förster
2008-07-10 19:08 ` Junio C Hamano
2008-07-10 19:42   ` Jakub Narebski
2008-07-10 19:52     ` Toralf Förster
2008-07-10 20:03     ` Junio C Hamano
2008-07-10 22:24       ` Johannes Schindelin [this message]
2008-07-10 22:52         ` Junio C Hamano
2008-07-10 23:08           ` Jakub Narebski
2008-07-10 23:47           ` Johannes Schindelin
2008-07-10 20:36     ` Linus Torvalds
2008-07-10 19:29 ` Johannes Schindelin
2008-07-11 13:39   ` Toralf Förster
2008-07-11 14:36     ` Johannes Schindelin
2008-07-11 14:44       ` Toralf Förster
2008-07-11 14:44     ` Dmitry Potapov
2008-07-11 14:58       ` Toralf Förster
2008-07-11 19:29         ` Dmitry Potapov
2008-07-11 19:57           ` Johannes Schindelin
2008-07-11 20:35             ` Johannes Schindelin

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=alpine.DEB.1.00.0807110022510.3279@eeepc-johanness \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=toralf.foerster@gmx.de \
    /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