unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Cc: "Romain Francoise" <romain@orebokech.com>,
	"Rémi Letot" <remi@lybrafox.be>
Subject: Re: Need help with ad-do-it, it loops
Date: Mon, 11 May 2009 08:38:55 +0200	[thread overview]
Message-ID: <e01d8a50905102338x54b6ff6ap47fea891d9ad55e9@mail.gmail.com> (raw)
In-Reply-To: <87iqk9oq03.fsf@elegiac.orebokech.com>

After trying to fix some bugs in nXhtml I still get reports from
Debian/Ubuntu users that it does not work with the Emacs snap-shots,
but it does if they compile Emacs themselves from CVS. The only things
I can think of that differs are:

- Source code: date seems unimportant, the snap-shots are fairly new.

- load-path: The list-load-path-shadows command does not show anything
special (at least not for Rémi, see
https://bugs.launchpad.net/nxhtml/+bug/369800).

- Debian's special startup.el: Not sure, but was not this just about load-path?

Anyone who can think of something else?

I have asked Romain for a diff (see below), but I am unsure if that
could be non-zero. Can someone please help us with this? Does "cvs
update" ensure that the diff is zero (as Romain assumes below)?


On Sun, May 10, 2009 at 12:44 AM, Romain Francoise <romain@orebokech.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> I have noticed that CVS can get out of synch so to say. At the end
>> of fetching from CVS (which I do in a loop to make sure that
>> everything is up to date) I have something like this
>
>>     cvs diff -b -u 2>&1 > %diff-file%
>
>> Do you do something like this too?
>
> Nope, but I usually do a cvs up just after checking out the tree
> just to make sure.  CVS checkouts aren't atomic, but my connection
> to Savannah is fast enough that the chances of having an incomplete
> change are pretty slim.
>




  parent reply	other threads:[~2009-05-11  6:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 22:15 Need help with ad-do-it, it loops Lennart Borgman
2009-05-08  9:01 ` AW: " klaus.berndl
2009-05-08 10:30   ` Lennart Borgman
2009-05-08 13:26 ` Stefan Monnier
2009-05-08 16:28   ` Lennart Borgman
2009-05-08 19:30     ` Stefan Monnier
2009-05-08 20:13       ` Lennart Borgman
2009-05-08 21:22         ` Lennart Borgman
2009-05-09 10:53           ` Lennart Borgman
2009-05-09 17:06             ` Sven Joachim
2009-05-09 17:26               ` Lennart Borgman
     [not found]             ` <e01d8a50905090405x2f1a5dc8s64d05cda7fc51366@mail.gmail.com>
     [not found]               ` <87iqk9oq03.fsf@elegiac.orebokech.com>
2009-05-11  6:38                 ` Lennart Borgman [this message]
2009-05-11 14:51                   ` Romain Francoise
2009-05-11 15:14                     ` Lennart Borgman

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=e01d8a50905102338x54b6ff6ap47fea891d9ad55e9@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=remi@lybrafox.be \
    --cc=romain@orebokech.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 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).