From: Andreas Schwab <schwab@linux-m68k.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Ramana Kumar <ramana.kumar@gmail.com>, git@vger.kernel.org
Subject: Re: recursive aliases
Date: Fri, 24 Sep 2010 00:49:45 +0200 [thread overview]
Message-ID: <m239t0gjna.fsf@igel.home> (raw)
In-Reply-To: <4C9B3B2A.2080604@op5.se> (Andreas Ericsson's message of "Thu, 23 Sep 2010 13:34:02 +0200")
Andreas Ericsson <ae@op5.se> writes:
> On 09/23/2010 08:07 AM, Ramana Kumar wrote:
>> Are recursive aliases in any way allowed?
>
> They're not just not allowed; they're not even possible.
$ git config alias.foo foo
$ git foo
fatal: recursive alias: foo
:-)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2010-09-23 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 6:07 recursive aliases Ramana Kumar
2010-09-23 11:34 ` Andreas Ericsson
2010-09-23 22:49 ` Andreas Schwab [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=m239t0gjna.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ramana.kumar@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).