threads / discuss / 2809

patches between commits

Subject: patches between commits

## tl;dr

3 messages between Dec 12, 2005 and Dec 12, 2005.

replies: 2people: 3as markdown or json

Bahadir Balban· Dec 12, 2005, 15:31 UTC · lore
Hi,
A very basic question - how could I generate patches across different commits?

Suppose I have a HEAD branch, which is the latest. And I want to generate `individual' patches for each commit I did since the beginning of development for this branch.

Secondly, is the sha1 of a tree what appears next to each commit when I type git-log? Is this the only command that lets us know the sha1's of commits?

Thanks, Bahadir

Alex Riesen· Dec 12, 2005, 17:33 UTC · re: Bahadir Balban · lore

Re: patches between commits

Bahadir Balban, Mon, Dec 12, 2005 16:31:12 +0100:
> Suppose I have a HEAD branch, which is the latest. And I want to
> generate `individual' patches for each commit I did since the
> beginning of development for this branch.

That is what I think "git format-patch <commit>" is for. It will generate patches to bring "<commit>" to HEAD.

> Secondly, is the sha1 of a tree what appears next to each commit when
> I type git-log? Is this the only command that lets us know the sha1's
> of commits?
"git rev-list", I think
Junio C Hamano· Dec 12, 2005, 17:54 UTC · re: Alex Riesen · lore

Re: patches between commits

Alex Riesen <raa.lkml@gmail.com> writes:
Show 7 quoted lines
> Bahadir Balban, Mon, Dec 12, 2005 16:31:12 +0100:
>> Suppose I have a HEAD branch, which is the latest. And I want to
>> generate `individual' patches for each commit I did since the
>> beginning of development for this branch.
>
> That is what I think "git format-patch <commit>" is for. It will
> generate patches to bring "<commit>" to HEAD.

Yes, but I think the real question Bahadir wants to know is what the <commit> parameter should be, if you want to export the whole history (I do not think there is any suitable argument to "format-patch" that does this).

>> Secondly, is the sha1 of a tree what appears next to each commit when
>> I type git-log? Is this the only command that lets us know the sha1's
>> of commits?

Depends on what you have, to ask the question "what are their object names?".

 - I have this commit, how do I find out its object name?
   E.g. I want to know the HEAD commit's object name, second to
   the last commit on "test" branch.
   $ git rev-parse --verify HEAD
   $ git rev-parse --verify test^
 - I have bunch of commits leading to the head of my "test"
   branch.  What are they?
   $ git rev-list test ;# unadorned list of object names and nothing else
   $ git rev-list --pretty test ;# this is git-log
   $ git whatchanged -m -M -p test ;# with patch in full glory

← back to recent threads