* patches between commits
@ 2005-12-12 15:31 Bahadir Balban
2005-12-12 17:33 ` Alex Riesen
0 siblings, 1 reply; 3+ messages in thread
From: Bahadir Balban @ 2005-12-12 15:31 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: patches between commits
2005-12-12 15:31 patches between commits Bahadir Balban
@ 2005-12-12 17:33 ` Alex Riesen
2005-12-12 17:54 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Alex Riesen @ 2005-12-12 17:33 UTC (permalink / raw)
To: Bahadir Balban; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: patches between commits
2005-12-12 17:33 ` Alex Riesen
@ 2005-12-12 17:54 ` Junio C Hamano
0 siblings, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2005-12-12 17:54 UTC (permalink / raw)
To: Alex Riesen; +Cc: git
Alex Riesen <raa.lkml@gmail.com> writes:
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-12-12 17:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-12 15:31 patches between commits Bahadir Balban
2005-12-12 17:33 ` Alex Riesen
2005-12-12 17:54 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox