From: Tassilo Horn <tassilo@member.fsf.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: [PATCH] Fix Gcc processing on IMAP
Date: Sun, 13 Feb 2011 16:15:39 +0100 [thread overview]
Message-ID: <877hd4dkys.fsf@member.fsf.org> (raw)
In-Reply-To: <87ipwohx3i.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 13 Feb 2011 07:40:01 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
Hi Ted,
> TH> as I've reported in <874o8enpi0.fsf@member.fsf.org>, Gcc is broken
> TH> in the current HEAD. I wanted to sit it out on an older working
> TH> revision till Lars is back, but unfortunately Ted did an interface
> TH> change in auth-sources that was synced to emacs, and now emacs has
> TH> an autoload cookie for some auth-sources function that is not
> TH> available in the older Gnus version...
>
> Sorry about that, Tassilo.
No, no. That you incidentially forced me to fix that bug is actually a
good thing, isn't it. ;-)
> I applied your patch. Lars can check it more thoroughly but it Works
> For Me :)
Great.
> TH> I have papers on file, but no push access for Gnus git. Could
> TH> someone please commit and push for me? (I could commit & push on
> TH> emacs bzr trunk, but I think this way is easier.)
>
> If you like, I can add you to the Git comitters.
That would be cool. Not that I have big plans for Gnus on my TODO list,
but I'm happy to fix a bug here and there when I stumble upon it. :-)
> I just need the output of "htpasswd -n tassilo".
I'll send it to you per private mail.
[Looking gnus.org for some docs...]
Oh, Gnus Resources still has a link to browse the old CVS. Someone
should remove it...
And on Gnus Distribution, there's some "should be verbatim but is not"
text in Committer Access...
Bye,
Tassilo
--
Sent from my Emacs
next prev parent reply other threads:[~2011-02-13 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 11:11 Tassilo Horn
2011-02-13 13:40 ` Ted Zlatanov
2011-02-13 15:15 ` Tassilo Horn [this message]
2011-02-14 15:18 ` Ted Zlatanov
2011-02-13 19:25 ` Lars Ingebrigtsen
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=877hd4dkys.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.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).