git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Horowitz <michael.horowitz@ieee.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: David Aguilar <davvid@gmail.com>,
	Dave Borowitz <dborowitz@google.com>, git <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: git alias question
Date: Mon, 2 Jan 2012 00:57:44 -0500	[thread overview]
Message-ID: <CAFLRbopp1ROfMqp3PVdUQ37_fdku2FtV-=pxuYk-YA-+_wgjPg@mail.gmail.com> (raw)
In-Reply-To: <m3zke8e2vh.fsf@localhost.localdomain>

Nice, works perfectly!  Didn't notice that was there, guess last time
I looked, I was using an older version.  I see it is in the git config
man page and all now.

Thanks,

Mike



On Sat, Dec 31, 2011 at 6:30 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>
> Michael Horowitz <michael.horowitz@ieee.org> writes:
>
> > The log operation does seem to make the most sense as the mechanism to
> > search for the results.  Making it work with difftool would work...
> > Not sure if "--log" to difftool or some other options as suggested in
> > the other thread would be most consistent UI-wise as stated, but
> > either would work for me.
> >
> > On a separate note, some environment variable like GIT_PREFIX with the
> > CWD would make the alias functionality more flexible.
>
> 1f5d271 (setup: Provide GIT_PREFIX to built-ins, 2011-05-25) is
> present in v1.7.7; 7cf16a1 (handle_alias: provide GIT_PREFIX to
> !alias, 2011-04-27) is in 1.7.6
>
> --
> Jakub Narebski

      reply	other threads:[~2012-01-02  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  1:27 git alias question Michael Horowitz
2011-12-29  3:21 ` Miles Bader
2011-12-29  5:32   ` Junio C Hamano
2011-12-29 17:08 ` Dave Borowitz
2011-12-30  1:59   ` David Aguilar
2011-12-31 21:31     ` Michael Horowitz
2011-12-31 23:30       ` Jakub Narebski
2012-01-02  5:57         ` Michael Horowitz [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

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

  git send-email \
    --in-reply-to='CAFLRbopp1ROfMqp3PVdUQ37_fdku2FtV-=pxuYk-YA-+_wgjPg@mail.gmail.com' \
    --to=michael.horowitz@ieee.org \
    --cc=davvid@gmail.com \
    --cc=dborowitz@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    /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).