git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Julliard <julliard@winehq.org>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: contrib/ area
Date: Sun, 19 Feb 2006 22:56:10 +0100	[thread overview]
Message-ID: <87lkw7dnd1.fsf@wine.dyndns.org> (raw)
In-Reply-To: <43F8E0B8.20508@vilain.net> (Sam Vilain's message of "Mon, 20 Feb 2006 10:18:48 +1300")

Sam Vilain <sam@vilain.net> writes:

> Alexandre Julliard wrote:
>> Is there interest in an emacs interface for git?  I posted a first
>> version (http://marc.theaimsgroup.com/?l=git&m=113313040724346&w=2)
>> some time ago, I'd be happy to send you a patch with my latest version
>> if you want to include it.
>
> Out of interest, why did you choose not to make this a vc- plug-in?

For the same reason that there are both vc-cvs and pcl-cvs modes, they
are completely different approaches to the user interface. The VC mode
is purely file-oriented, and is very limited in its ability to handle
project-wide changes. It has its uses, but IMO there's no way to
exploit the full capabilities of a tool like git (or even CVS) with
the VC interface.

-- 
Alexandre Julliard
julliard@winehq.org

  reply	other threads:[~2006-02-19 21:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 11:07 contrib/ area Junio C Hamano
2006-02-17 12:05 ` Alexandre Julliard
2006-02-17 12:24   ` Martin Langhoff
2006-02-18  6:49   ` Junio C Hamano
2006-02-18 16:49     ` Alexandre Julliard
2006-02-19 21:18   ` Sam Vilain
2006-02-19 21:56     ` Alexandre Julliard [this message]
2006-02-17 12:36 ` Aneesh Kumar
2006-02-18  6:50   ` Junio C Hamano
2006-02-18  8:38     ` Aneesh Kumar
2006-02-18  9:02       ` Junio C Hamano
2006-02-21  1:41 ` Ben Clifford
2006-02-21  3:58   ` Junio C Hamano
     [not found]     ` <b7bc5ebe0602202110l53418b32q@mail.gmail.com>
2006-02-21  7:43       ` Petr Baudis

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lkw7dnd1.fsf@wine.dyndns.org \
    --to=julliard@winehq.org \
    --cc=git@vger.kernel.org \
    --cc=sam@vilain.net \
    /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.
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 NNTP newsgroup(s).