git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: git@vger.kernel.org
Subject: Re: [EGIT PATCH] Show diffs for changed files under a new or deleted directory.
Date: Mon, 18 Feb 2008 07:44:57 +0100	[thread overview]
Message-ID: <200802180744.57757.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <47B9110E.90707@intelinet.com.br>

måndagen den 18 februari 2008 skrev du:
> The Differencer I changed was actually a bug. If you say that the files 
> left in the left pane are Differencer.ADDITION, then the ones left on 
> the right pane _must_ be Differencer.DELETION. It just doesn't make 
> sense to say that files not on the old tree but on the new tree are 
> addition, and at the same time that files on the old tree but not on the 
> new tree are also addition.
Ok, I see. I'll test it a little and push soon.
> > I'd love to see a unit test for your code since, even if it works, it is very easy
> > to break again.
> >   
> Ok, I'll get a look on the test cases and probably write something when 
> I get back into these compare issues. That if somebody else doesn't do 
> it before me, of course :)

Not very likely within a short time frame, though I want do the excersize. Unfortunately I have too many open branches right now to add yet another. The original author (cough, cough) didn't do it. I was so happy and pleased, at them time, to see it work at all so easiliy :) . I've written some tests for other functions, so I guess it's mostly about setting up some more infrastructure to make testing reasonably simple.

-- robin

      reply	other threads:[~2008-02-18  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 15:55 [EGIT PATCH] Show diffs for changed files under a new or deleted directory Roger C. Soares
2008-02-17 15:05 ` Robin Rosenberg
2008-02-18  5:01   ` Roger C. Soares
2008-02-18  6:44     ` Robin Rosenberg [this message]

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=200802180744.57757.robin.rosenberg@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=rogersoares@intelinet.com.br \
    /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).