unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: John Wiegley <johnw@newartisans.com>
Cc: Glenn Morris <rgm@gnu.org>,
	Carsten Dominik <dominik@science.uva.nl>,
	emacs-devel@gnu.org
Subject: Re: recent changes to org files
Date: Mon, 22 Oct 2007 20:57:00 -0400	[thread overview]
Message-ID: <jwvprz6zm1w.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m28x5ukb9m.fsf@newartisans.com> (John Wiegley's message of "Mon\, 22 Oct 2007 18\:57\:57 -0400")

>> When you install changes to org files, will you please look at the actual
>> diffs before you do so, and only apply the bits that make sense?

> Hmm... I'm just installing what the author distributes.  It was never
> mentioned to me that the Emacs developers might be making changes directly to
> his files without exporting those changes back to his own sources.

> Perhaps it would be better if I left it to the author to merge any Emacs CVS
> changes into his code and then check them in directly, rather than posting the
> contents of his new releases verbatim to CVS.  What do you think, Carsten?

To me the rule goes as follows: I only install patches, not files.
That usually takes core of those problems: if the author's version disagrees
with the CVS version I get a conflict when I try to apply the patch.


        Stefan

  reply	other threads:[~2007-10-23  0:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 22:28 recent changes to org files Glenn Morris
2007-10-22 22:57 ` John Wiegley
2007-10-23  0:57   ` Stefan Monnier [this message]
2007-10-23  9:18     ` Carsten Dominik
2007-10-23  9:48     ` Carsten Dominik
2007-10-23 10:06       ` Juanma Barranquero
2007-10-23 10:08       ` David Kastrup
2007-10-23 10:36         ` Carsten Dominik
2007-10-23 11:11           ` Juanma Barranquero
2007-10-23 11:39             ` Carsten Dominik
2007-10-23 11:44               ` Juanma Barranquero
2007-10-23 11:54                 ` Carsten Dominik
2007-10-23 12:06                   ` Juanma Barranquero
2007-10-23 20:19                     ` Carsten Dominik
2007-10-23 21:58                       ` Stefan Monnier
2007-10-23 11:16           ` David Kastrup
2007-10-23 11:34             ` Carsten Dominik
2007-10-23 11:49               ` Juanma Barranquero
2007-10-24  2:50                 ` Richard Stallman
2007-10-23 11:59               ` David Kastrup
2007-10-23 12:06                 ` Carsten Dominik
2007-10-24  2:50                 ` Richard Stallman
2007-10-23 14:43               ` Stefan Monnier
2007-10-23 20:09                 ` Carsten Dominik
2007-10-24  2:50             ` Richard Stallman
2007-10-24  3:33               ` Carsten Dominik
2007-10-29  7:30                 ` Glenn Morris
2007-10-29 22:21                   ` John Wiegley
2007-10-30  6:34                   ` Carsten Dominik
2007-10-23 10:30       ` Miles Bader
2007-10-23  2:11   ` Miles Bader

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=jwvprz6zm1w.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dominik@science.uva.nl \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=rgm@gnu.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).