unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: John Wiegley <johnw@newartisans.com>,
	emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Glenn Morris <rgm@gnu.org>
Subject: Re: recent changes to org files
Date: Tue, 23 Oct 2007 22:19:37 +0200	[thread overview]
Message-ID: <D3DB32BB-3229-48BF-A03D-466CBA2AE635@gmail.com> (raw)
In-Reply-To: <f7ccd24b0710230506p5f22a235s240c1eb96ab730fe@mail.gmail.com>


On Oct 23, 2007, at 2:06 PM, Juanma Barranquero wrote:

> On 10/23/07, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
>> I was referring to this statement.  It is not enough to install only
>> patches,
>> I also need to actively monitor changes that are made by others.
>
> OK, now I understand. Thanks.
>
> However, someone has to track the changes. Either you track the
> changes in the CVS, or whomever intends to fix or change anything in
> the CVS must check that his changes don't conflict with your version
> (and that makes having Org in the CVS somewhat irrelevant), or the
> person goes ahead, does the change and sends it to you (and then, if
> your copy varies much faster than the CVS one, conflicts are bound to
> happen and effort is wasted).

Well, I am doing this.  I am checking changes made in the CVS and
incorporate them into my copy.  I never said that I was not doing this.
I don't know how this discussion came to suggest that I am not doing
it.

However, I made a mistake, partly because too many people made a
mistake became involved in the loop and my own versioning system
seems not good enough.  I will work on this, but I do make mistakes.
And: it would be helpful for me if there was a system through which I
could automatically get patches of changes to Emacs CVS versions
of my files.  I don't think it is too much to ask.  Regulars in the  
emacs
development community probably know that, even though org is
very stable and has only had very few bug reports inside Emacs,
I am still making big changes often.  So notification, better a request
for double checking changes to the files from others is, I think,
reasonable to ask for.

- Carsten

  reply	other threads:[~2007-10-23 20:19 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
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 [this message]
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=D3DB32BB-3229-48BF-A03D-466CBA2AE635@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --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).