git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: git@vger.kernel.org
Subject: infinite loop in git-send-email with alias files
Date: Thu, 16 Jul 2009 21:10:00 -0400	[thread overview]
Message-ID: <8bd0f97a0907161810w22726ffdye5c8d64719b77b53@mail.gmail.com> (raw)

i was setting up an aliasesfile for git-send-email, but in doing so, i
inadvertently made a typo creating an infinite loop.  i didnt notice
right away, but i did notice when `git-send-email` hung using 100% of
a cpu.

simple way to reproduce:
$ $ git config sendemail.aliasesfile
.git/mail
$ git config sendemail.aliasfiletype
mutt
$ cat .git/mail
alias a b
alias b a
$ git send-email HEAD^ --to a
<hit enter a few times and watch it hang>

noticed with 1.6.3.3, but seems to be in 1.6.4-rc1 too
-mike

             reply	other threads:[~2009-07-17  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17  1:10 Mike Frysinger [this message]
2009-07-23 11:09 ` infinite loop in git-send-email with alias files Jeff King
2009-07-23 12:30   ` Johannes Sixt
2009-07-23 13:54     ` Jeff King

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=8bd0f97a0907161810w22726ffdye5c8d64719b77b53@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=git@vger.kernel.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).