MIME-Version: 1.0
X-RT-Interface: Web
Content-Transfer-Encoding: binary
In-Reply-To: <rt-4.4.1-10156-1504914900-172.45186-0-0@isc.org>
Content-Disposition: inline
X-RT-Original-Encoding: utf-8
Content-Type: text/plain; charset="utf-8"
References: <RT-Ticket-45186@isc.org>
 <rt-4.2.8-2611-1493950528-1432.45186-4-0@isc.org>
 <rt-4.2.8-30801-1495916960-592.45186-4-0@isc.org>
 <rt-4.4.1-30483-1504183952-736.45186-4-0@isc.org>
 <6166e45c-cd9c-66fd-f91e-5fbaa835f9cd@isc.org>
 <rt-4.4.1-11937-1504900325-304.45186-7-0@isc.org>
 <20170908214407.GC44967@isc.org>
 <rt-4.4.1-11997-1504907050-1228.45186-7-0@isc.org>
 <20170908235335.3589B84BD3A9@rock.dv.isc.org>
 <rt-4.4.1-10156-1504914900-172.45186-0-0@isc.org>
Message-ID: <rt-4.4.1-4791-1505780241-1813.45186-0-0@isc.org>
X-Mailer: MIME-tools 5.508 (Entity 5.508)
RT-Send-CC:
Content-Length: 1157

The tests look fine. We should still plan to add more testing in the future.

On Fri Sep 08 16:55:00 2017, marka wrote:
> 
> In message <rt-4.4.1-11997-1504907050-1228.45186-7-0@isc.org>, "Evan
> Hunt via R
> T" writes:
> > [ NOTE: This is a comment.  It is not sent to the Requestor(s): ]
> >
> > On Fri, Sep 08, 2017 at 07:52:06PM +0000, Ray Bellis via RT wrote:
> > > I still find them massively convenient when trying to see what has
> > > actually changed in a branch when master has subsequently diverged
> > > from
> > > that point.
> >
> > Use "git diff master...<branch>".
> >
> > Note: "master <branch>" means one thing, "master..<branch>" (two
> > dots)
> > means another thing, and "master...<branch>" (three dots) is the one
> > you
> > want.  It shows the changes that have been applied to the branch
> > since the branch point, regardless of what's in the master branch
> > now.
> > It's exactly the same as diffing against a base tag.
> 
> It's actually better as you can merge master back into the branch
> and see how it differs from master as of this merge.
> 
> > --
> > Ticket History: https://bugs.isc.org/Ticket/Display.html?id=45186