Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: patches between commits
Date: Mon, 12 Dec 2005 09:54:45 -0800	[thread overview]
Message-ID: <7vu0dei4ka.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20051212173352.GA3007@steel.home

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

      reply	other threads:[~2005-12-12 17:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vu0dei4ka.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox