unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: keramida@ceid.upatras.gr (Giorgos Keramidas)
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Katsumi Yamaoka <yamaoka@jpl.org>,
	ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Tue, 09 Jul 2013 23:42:22 +0200	[thread overview]
Message-ID: <878v1fs94x.fsf@randomsample.de> (raw)
In-Reply-To: <67um8rbo6bpisw.fsf@saturn.laptop> (Giorgos Keramidas's message of "Tue, 09 Jul 2013 22:41:51 +0200")

Giorgos Keramidas writes:
> Great!  Now we know at least why this is triggered.  Looking at the
> diffs between emacs-24 and trunk of Emacs I can see that this function
> indeed only exists in the trunk:

It was recently synced from Gnus git.

> If I'm reading this function right, then _every_ time someone runs Gnus
> from the trunk of Emacs they would have to do an 'initial sync' of all
> their groups, because "Gnus v5.13" will never be >= "Ma Gnus.*".

This is not the desired behavior, of course. It's a bug which happens
because of the different versioning schemes used in Gnus git and Emacs
trunk. I like Ted's suggestion on how to fix it, and if no one objects
or beats me to it, I'll commit that tomorrow.

-David



  reply	other threads:[~2013-07-09 21:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 10:40 Emacs trunk and Gnus master are fully sync'd now Katsumi Yamaoka
2013-07-02 16:52 ` Giorgos Keramidas
2013-07-06 15:21   ` Lars Ingebrigtsen
2013-07-06 15:44     ` David Engster
2013-07-06 18:45       ` David Engster
2013-07-06 20:03         ` David Engster
2013-07-07 13:27           ` Giorgos Keramidas
2013-07-07 13:24       ` Giorgos Keramidas
2013-07-07 19:51         ` David Engster
2013-07-08 13:16           ` Giorgos Keramidas
2013-07-08 18:24             ` David Engster
2013-07-09 11:08               ` Giorgos Keramidas
2013-07-09 15:34                 ` David Engster
2013-07-09 18:16                   ` Giorgos Keramidas
2013-07-09 19:33                     ` David Engster
2013-07-09 19:39                       ` Ted Zlatanov
2013-07-09 20:41                       ` Giorgos Keramidas
2013-07-09 21:42                         ` David Engster [this message]
2013-07-10 15:32                           ` Ted Zlatanov
2013-07-10 19:17                           ` David Engster
2013-07-11 17:12                             ` Giorgos Keramidas
2013-07-18 13:31                           ` Lars Magne Ingebrigtsen
2013-07-18 15:42                             ` Giorgos Keramidas
2013-07-18 16:55                               ` David Engster
2013-07-18 17:15                                 ` Giorgos Keramidas
2013-07-30 14:56                               ` Lars Magne Ingebrigtsen
2013-07-30 19:58                                 ` Giorgos Keramidas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878v1fs94x.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=keramida@ceid.upatras.gr \
    --cc=larsi@gnus.org \
    --cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).