RE: Any way to get complete diff up to a tag?

From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Date: May 7, 2010, 04:17 UTC
Message-ID: <A612847CFE53224C91B23E3A5B48BAC744829D68C7@xmail3.se.axis.com>
In-Reply-To: <AANLkTilOOYlrQ5hfgxFnCIG4Qp5RE_EbfzP6vkfqBAJM@mail.gmail.com>

Show 26 quoted lines

> -----Original Message-----
> From: git-owner@vger.kernel.org
> [mailto:git-owner@vger.kernel.org] On Behalf Of Knittl
> Sent: den 6 maj 2010 17:44
> To: Peter Kjellerstedt
> Cc: git@vger.kernel.org
> Subject: Re: Any way to get complete diff up to a tag?
>
> On Thu, May 6, 2010 at 11:27 AM, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> > Basically, what I think I am asking for is a way to specify the
> > empty parent of the initial commit, i.e., where v1.7.1~1000000 would
> > end up. I can see this being useful in at least one other case as
> > well, namely when doing an interactive rebase to allow the initial
> > commit to be rebased (something I have wanted to do a couple of
> > times...)
>
> wait, let me get this straight. you want to diff some tag against the
> empty parent of the root commit (empty tree)?
>
> which in turn means you will get a diff, where all lines in all files
> existing in the tree that tag references are added. all files get
> basically prefixed with + and have header information (filename). what
> purpose has such a diff?
>
> regards, daniel

Well, I can see a couple of purposes, but in my case I have a tool post-processing the generated diff. And to it there is no difference regarding what point was used as the start of the diff, whether it was the empty tree (i.e., a diff containing everything), some commit in the middle, or the last commit (i.e., an emptry diff). All it wants is a diff.

//Peter