From: Sven Joachim <svenjoac@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: auth-source patch for secure logging
Date: Fri, 17 Jul 2009 21:42:18 +0200 [thread overview]
Message-ID: <87k52714h1.fsf@turtle.gmx.de> (raw)
In-Reply-To: <87iqhrkwpq.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 17 Jul 2009 13:09:37 -0500")
On 2009-07-17 20:09 +0200, Ted Zlatanov wrote:
> On Fri, 17 Jul 2009 14:01:21 -0400 Glenn Morris <rgm@gnu.org> wrote:
>
> GM> Ted Zlatanov wrote:
> GM> It seems it got checked into the branch.
>>>
>>> I checked it into the Gnus CVS trunk. It should have been synchronized
>>> with the Emacs CVS trunk only. What branch are you referring to?
>
> GM> The EMACS_23_1_RC release branch in Emacs CVS.
>
> GM> http://lists.gnu.org/archive/html/emacs-diffs/2009-07/msg00480.html
>
> Right, I know about this branch, I was just making sure we're discussing
> the same thing. I don't know how it got into the 23.1 RC branch, sorry.
Relating trunks and branches, should not Gnus branch as well for the
5.12 release? I thought that this release was planned to happen at
about the same time as the Emacs 23.1 release.
> As I mentioned, it was not my intention that it would. Maybe Miles'
> synchronization script misfired.
BTW, is it agreed that Gnus trunk should continue to be synced with the
Emacs trunk?
Cheers,
Sven
prev parent reply other threads:[~2009-07-17 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 14:23 auth-source patch for secure logging Ted Zlatanov
2009-07-16 14:33 ` Ted Zlatanov
2009-07-16 15:55 ` Davis Herring
2009-07-16 16:21 ` Ted Zlatanov
2009-07-16 15:32 ` Chong Yidong
2009-07-16 16:15 ` Ted Zlatanov
2009-07-16 18:09 ` Ted Zlatanov
2009-07-17 17:31 ` Glenn Morris
2009-07-17 17:53 ` Ted Zlatanov
2009-07-17 18:01 ` Glenn Morris
2009-07-17 18:09 ` Ted Zlatanov
2009-07-17 18:35 ` Chong Yidong
2009-07-18 17:21 ` Chong Yidong
2009-07-17 19:42 ` Sven Joachim [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=87k52714h1.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.