emacs-devel
[Top][All Lists]
Advanced

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

Re: Referring to revisions in the git future.


From: Eric S. Raymond
Subject: Re: Referring to revisions in the git future.
Date: Thu, 30 Oct 2014 07:51:28 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

David Kastrup <address@hidden>:
> At any rate, that's not an on-site resource for somebody having
> installed a full copy of Emacs.  One of the main points of a distributed
> version control system is the ability to work offline.
> 
> "There is some instruction somewhere on the Internet" is not a
> sufficient excuse for leaving Emacs without any resources pointing out
> the desired workflow for Emacs developers.
> 
> If "the wiki" is an authoritive source for the workflow of Emacs
> developers, it means that anybody who wants to can tell the Emacs
> developers how to do their work.

You may be right. But this is not a git transition issue.

There is some in-tree workflow documentation in admin/notes/repo.  It
isn't very good.  My transition patch fixes it to refer to git commands
rather than bzr ones (and deletes some sections about things like
loggerhead that will no longer be relevant).  

It still isn't very good, but reworking it is out of scope for what
I'm trying to get done before conversion day.  After that, we can have
a *separate* conversation about the proper role of the in-tree notes
vs. the wiki, whether access to the wiki should be restricted in some
way, etc.

I have no particular opinions about those matters.  I do have both the
ability and the willingness to write good documentation, so I expect
I will end up doing a lot of the writing if we decide to reorganize.  

What I am not willing to do is dive into that matter *right now*.
The transition job is huge and it's not done yet. (Pull the repo
containing my transition machinery sometime and browse it.  You
should find the experience ... enlightening.)

It's all to the good that the transition is causing people to pay
attention to back issues that they normally ignore, but when these
come up please try to queue them for later rather than talking as
if the solution is a requirement for the transition itself.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>



reply via email to

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