git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: mutt aliases file not working
Date: Fri, 29 Oct 2010 09:04:04 -0700	[thread overview]
Message-ID: <4CCAF074.2080701@linux.intel.com> (raw)
In-Reply-To: <4CCAA735.1030805@drmicha.warpmail.net>

On 10/29/2010 03:51 AM, Michael J Gruber wrote:
> Darren Hart venit, vidit, dixit 27.10.2010 23:38:
>> For whatever reason, which I'm sure is user error, I haven't been
>> able to get mutt aliases to work, while mailrc works fine:
>>
>> $ mkdir aliases.git
>> $ cd !$
>> $ git init
>> Initialized empty Git repository in /home/dvhart/aliases.git/.git/
>> $ echo "joe Joe Blow joe@foobar.com">  muttaliases
>
> How about:
>
> echo 'alias joe Joe Blow<joe@foobar.com>'>  muttaliases

Indeed, that fixes it. I checked my reference for the mutt aliases 
format and apparently missed the "alias " clearly printed out there. My 
apologies.

The git send-email man page is surely sufficient for users of mutt, 
mailrc, pine, elm, gnus as they already have working configurations, but 
for those of us that use a different MUA and just want to get some sort 
of an address book for git, it would be nice to define these formats - 
it would only take one line per format type.

Thanks!

Darren Hart

>
>> $ git add muttaliases
>> $ git commit -m "aliases file"
>> [master (root-commit) b71ae4a] aliases file
>>   1 files changed, 1 insertions(+), 0 deletions(-)
>>   create mode 100644 muttaliases
>> $ git config sendemail.aliasesfile `pwd`/muttaliases
>> $ git config sendemail.aliasfiletype mutt
>> $ cat .git/config
>> [core]
>> 	repositoryformatversion = 0
>> 	filemode = true
>> 	bare = false
>> 	logallrefupdates = true
>> [sendemail]
>> 	aliasesfile = /home/dvhart/aliases.git/muttaliases
>> 	aliasfiletype = mutt
>> $ git send-email --to joe -1
>> /tmp/l0xCEC7o3d/0001-aliases-file.patch
>> Who should the emails appear to be from? [Darren Hart<darren@dvhart.com>]
>> Emails will be sent from: Darren Hart<darren@dvhart.com>
>> Message-ID to be used as In-Reply-To for the first email?
>> (mbox) Adding cc: Darren Hart<darren@dvhart.com>  from line 'From: Darren Hart<darren@dvhart.com>'
>>
>> From: Darren Hart<darren@dvhart.com>
>> To: joe
>>
>>      ^ when using a mailrc fail this expands to joe@foobar.com
>>
>> Cc: Darren Hart<darren@dvhart.com>
>> Subject: [PATCH] aliases file
>> Date: Wed, 27 Oct 2010 14:29:10 -0700
>> Message-Id:<1288214950-13695-1-git-send-email-darren@dvhart.com>
>> X-Mailer: git-send-email 1.7.1
>>
>> Send this email? ([y]es|[n]o|[q]uit|[a]ll): ^C
>>
>> $ stty: standard input: Input/output error
>> ^C
>>
>> Am I doing something obviously wrong?
>>
>


-- 
Darren Hart
Embedded Linux Kernel

      reply	other threads:[~2010-10-29 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 21:38 mutt aliases file not working Darren Hart
2010-10-29 10:51 ` Michael J Gruber
2010-10-29 16:04   ` Darren Hart [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=4CCAF074.2080701@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=git@drmicha.warpmail.net \
    --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).