git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Finding changes in one branch not in two other branch

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2008, 19:05 UTC
Message-ID
<7viqyjx7jl.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<cc723f590804150421j689ef4b1o57b97c937e23db99@mail.gmail.com>
"Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
Show 9 quoted lines
> To show a workflow:
>
> kernel releases 2.6.20 and the project release patchset on top of 2.6.20
> kernel release 2.6.21 and project release patchset on top of 2.6.21
>
> The second release involve some bug fixes for the project.
>
> The intention is to find out what changed in project with the release of
> 2.6.21 patchset
That depends on your definition of what a patchset is.

If it is a set of files, each file has a patch to one or more files to implement a logically independent and complete change (i.e. corresponds to what a commit should be), then you can run git-patch-id on each of them to find the duplicates in these two sets (you do not need a git repository to do this, as patch-id is a freestanding operation).

If you mean a single file that contains the difference between the vanilla
2.6.21 and their version, then you cannot do much better than running
interdiff, I'd guess.
Previous: Aneesh Kumar
Message 2 of 2 in “Finding changes in one branch not in two other branch”
  1. Aneesh KumarApr 15, 2008
  2. Junio C HamanoApr 15, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.