unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Alexandre Julliard <julliard@winehq.org>
Cc: Dan Nicolaescu <dann@ics.uci.edu>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: adding new modes
Date: Fri, 18 May 2007 12:04:26 +0200	[thread overview]
Message-ID: <867ir6o3bp.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87abw231m5.fsf@wine.dyndns.org> (Alexandre Julliard's message of "Fri\, 18 May 2007 11\:46\:58 +0200")

Alexandre Julliard <julliard@winehq.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> vc-git is not of release-quality (C-u C-x v = usually chokes while
>> trying to propose a "previous version").  However, the Emacs 23
>> release is not exactly around the door, and having it synched into
>> Emacs-CVS might be nice.  At the current point of time, it is
>> maintained in git's git repository.  Not all people with write access
>> there will have a copyright assignment.  So one would have to check
>> who actually wrote stuff in it.
>
> I'm the main author of vc-git.el and git.el, and I'd be happy to sign
> the needed paperwork if you want to use them. I think most of the
> changes done by other people would be in the tiny change category, or
> I can rewrite them if needed.
>
> It's true that vc-git is not very good at the moment, it's a quick
> hack I put together because people were requesting it but I don't
> really use it myself, so I'd be happy for someone to take over
> maintenance. git.el is in better shape, and much more useful IMHO.

There is also git-blame which currently feels like it has an
interactivity issue: it should probably not parse everything it gets
at once, but rather in smaller chunks via an idle-hook.

I'll send you the assignment request in a separate mail.  Personally,
I think that Emacs should support git out of the box: git is actually
the most "bazaaresque" system I know: one does not need to put
identification into files, and one can even split large files up and
stuff and move and rename them without telling the version control
system, and it will still manage to reasonably track stuff.  And one
does not need access to non-local repositories, and it is quite
convenient for developing on local shadow branches of Subversion/CVS
checkouts without needing upstream support.

Some of its concepts might not fit perfectly within the VC framework
(like the index file and parts of its branching and patchset model):
for that reason alone, it would be good to continue development of the
git Elisp packages in the Emacs tree itself: that way, vc can be
adapted if necessary.

I'll leave it to you to contact other developers, ask them to consider
the assignment, and send them the request forms: if you need
additional explanations about why they are required and what they
imply, feel free to contact me, or the copyright clerk.

And thanks!

-- 
David Kastrup

  reply	other threads:[~2007-05-18 10:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 17:48 ruby-mode Seiji Zenitani
2007-05-13 18:05 ` ruby-mode David Kastrup
2007-05-13 18:54   ` ruby-mode Thien-Thi Nguyen
2007-05-16  1:16     ` ruby-mode Seiji Zenitani
2007-05-14 17:16 ` ruby-mode Stefan Monnier
2007-05-16 16:49   ` adding new modes [was: Re: ruby-mode] Dan Nicolaescu
2007-05-17 14:55     ` adding new modes Stefan Monnier
2007-05-17 17:08       ` David Kastrup
2007-05-18  9:46         ` Alexandre Julliard
2007-05-18 10:04           ` David Kastrup [this message]
2007-07-22 22:48           ` new VC backend: vc-git added, please test (was: Re: adding new modes) Dan Nicolaescu
2007-07-22 23:12             ` new VC backend: vc-git added, please test David Kastrup
2007-07-23  1:32               ` Dan Nicolaescu
2007-07-23  5:16                 ` David Kastrup
2007-07-23 14:45                   ` Dan Nicolaescu
2007-05-18 13:00       ` adding new modes Richard Stallman
2007-05-17 21:04     ` adding new modes [was: Re: ruby-mode] Dan Nicolaescu
2007-05-17 22:25       ` adding new modes Stefan Monnier
2007-05-17 21:31     ` adding new modes [was: Re: ruby-mode] Richard Stallman
2007-05-17 22:12       ` Dan Nicolaescu
2007-05-28  8:11     ` adding new modes Miles Bader
2007-05-28  8:29       ` Juanma Barranquero
2007-05-28  8:37         ` David Kastrup
2007-05-28 11:01           ` Miles Bader
2007-05-28  9:32         ` Miles Bader
2007-05-29  0:02       ` Richard Stallman
2007-10-05 19:28         ` Glenn Morris
2007-10-07  0:30           ` lua-mode Richard Stallman
2007-10-07  6:56             ` lua-mode Glenn Morris
2007-10-07 17:26               ` lua-mode Juergen Hoetzel
2007-10-09  1:14                 ` lua-mode Richard Stallman

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=867ir6o3bp.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=julliard@winehq.org \
    --cc=monnier@iro.umontreal.ca \
    /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).