unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Barry OReilly <gundaetiapo@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Two feature ideas for diffs
Date: Thu, 7 Nov 2013 13:49:42 -0500	[thread overview]
Message-ID: <CAFM41H2Rid5F0FV65bovDvWSRwNF0Tj=f6p0jD9PV_VbqvnPJw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

> Nice, but it's a pity it's written as git-specific. Git should only
> be one of the backends and the frontend should call the appropriate
> backend after checking what VC the file is under.

It should operate on unified diffs and provide the customization for
how to obtain the unified diffs, eg 'git diff'.

Dmitry, can diff-hl be used to review patch files distributed as diff
files without relying on a VCS?

[-- Attachment #2: Type: text/html, Size: 493 bytes --]

             reply	other threads:[~2013-11-07 18:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 18:49 Barry OReilly [this message]
2013-11-07 22:05 ` Two feature ideas for diffs Dmitry Gutov
  -- strict thread matches above, loose matches on Subject: below --
2013-11-07 17:08 Tom
2013-11-07 17:25 ` nhs
2013-11-07 17:39   ` Tom
2013-11-07 17:58     ` Dmitry Gutov
2013-11-07 18:24       ` Tom
2013-11-07 19:09       ` Stefan Monnier
2013-11-07 19:30         ` Dmitry Gutov
2013-11-07 20:00           ` Stefan Monnier
2013-11-08 22:58       ` Michael Heerdegen
2013-11-09  2:30         ` Óscar Fuentes
2013-11-09  2:59           ` Michael Heerdegen
2013-11-09 13:34             ` Stefan Monnier
2013-11-09 22:58               ` Michael Heerdegen
2013-11-09 13:37           ` Stefan Monnier
2013-11-09 15:02             ` Óscar Fuentes
2013-11-10 13:24               ` Stefan Monnier
2013-11-07 18:11 ` Dmitry Gutov
2013-11-07 18:33   ` Tom
2013-11-08  1:29   ` Ivan Andrus
2013-11-07 19:11 ` Stefan Monnier

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='CAFM41H2Rid5F0FV65bovDvWSRwNF0Tj=f6p0jD9PV_VbqvnPJw@mail.gmail.com' \
    --to=gundaetiapo@gmail.com \
    --cc=emacs-devel@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).