[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch vs. overwrite in bzr

From: Bastien
Subject: Re: patch vs. overwrite in bzr
Date: Fri, 06 Apr 2012 11:20:18 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Bastien <address@hidden>
>> Cc: Stefan Monnier <address@hidden>,  address@hidden,  address@hidden
>> Date: Fri, 06 Apr 2012 10:29:13 +0200
>> Regular Org testers don't want to rebuild Emacs each time they have 
>> to test a new feature in Org.
> Why would they need to do that?  Org is not preloaded into Emacs, so
> all you need is compile the new Org files and perhaps restart the
> Emacs session, but not rebuild Emacs.

Right.  But there are other problems.  

- Updating to the latest Org via `bzr update' would take longer compared
  to the current `git pull' (several factors here...)

- Some people don't have access to their Emacs installation (at work,
  for example) and still want the latest Org.

And surely more.  In any case, I'm all in favor of having the most
recent Org in Emacs trunk regularily, but migrating the development
of Org from the separate git repo to Emacs bzr repo is a no-go.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]