Git development
 help / color / mirror / Atom feed
From: Rocco Rutte <pdmef@gmx.net>
To: git@vger.kernel.org
Subject: Re: Creating diffs
Date: Thu, 3 Aug 2006 14:58:50 +0000	[thread overview]
Message-ID: <20060803145850.GK5016@robert.daprodeges.fqdn.th-h.de> (raw)
In-Reply-To: <eat29j$lil$1@sea.gmane.org>

Hi,

* Jakub Narebski [06-08-03 16:47:49 +0200] wrote:

>The patches are:
>  http://www.gelato.unsw.edu.au/archives/git/0607/24325.html
>  http://www.gelato.unsw.edu.au/archives/git/0607/24326.html

Hmm, ok, thanks for the pointer. What made me wonder in the first place 
is that the format differs from the diff-two-branches case because I 
assumed the algorithm basically is what I want to do (except it just 
does not exclude files) (i.e. diff-two-trees := get changed files and 
for each file, dump diff).

And what about the reverted diff contents? I don't know git too well so 
it take me quite long to provide a patch...

   bye, Rocco
-- 
:wq!

  reply	other threads:[~2006-08-03 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 12:29 Creating diffs Rocco Rutte
2006-08-03 12:39 ` Jakub Narebski
2006-08-03 14:47   ` Jakub Narebski
2006-08-03 14:58     ` Rocco Rutte [this message]
2006-08-03 18:45   ` Junio C Hamano
2006-08-03 18:22 ` Junio C Hamano

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=20060803145850.GK5016@robert.daprodeges.fqdn.th-h.de \
    --to=pdmef@gmx.net \
    --cc=git@vger.kernel.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox