From: Jeff Garzik <jgarzik@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, git@vger.kernel.org
Subject: Re: [howto] Kernel hacker's guide to git, updated
Date: Fri, 30 Sep 2005 10:11:06 -0400 [thread overview]
Message-ID: <433D477A.4010009@pobox.com> (raw)
In-Reply-To: <7v64si4von.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>>2) What is the easiest way to obtain a list of changes present in
>>repository B, that are not present in repository A? I used to use
>>git-changes-script [hacked cg-log script] for this:
>
>
> I think I still have the copy you sent to the list. If you do
> not mind me placing in the master branch just holler -- better
> yet please send a patch with commit log and signoff to add the
> latest, and I will apply it.
It's archived here:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/git-changes-script
but it needs a git expert (read: not me :)) to fix it up for the very
latest git-core stuff.
Currently, using 'git-changes-script -L ../linux-2.6' spits out
> --------------------------
> commit 2fca877b68b2b4fc5b94277858a1bedd46017cde
> usage: git-cat-file [-t | -s | <type>] <sha1>
>
> --------------------------
> commit ff40c6d3d1437ecdf295b8e39adcb06c3d6021ef
> usage: git-cat-file [-t | -s | <type>] <sha1>
>
> --------------------------
> commit 8bf62ecee58360749c5f0e68bc97d5e02a6816b1
> usage: git-cat-file [-t | -s | <type>] <sha1>
>
> --------------------------
Regards,
Jeff
next prev parent reply other threads:[~2005-09-30 14:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 11:03 [howto] Kernel hacker's guide to git, updated Jeff Garzik
2005-09-29 15:18 ` David Leimbach
2005-09-29 16:03 ` Alberto Patino
2005-09-29 16:13 ` David Leimbach
2005-09-29 19:08 ` Oliver Neukum
2005-09-29 19:34 ` Jon Loeliger
2005-09-29 19:38 ` Oliver Neukum
2005-09-30 7:37 ` Junio C Hamano
2005-09-30 8:36 ` Oliver Neukum
2005-09-30 16:39 ` Linus Torvalds
2005-09-29 20:02 ` Dave Jones
2005-09-29 20:07 ` Anton Altaparmakov
2005-09-29 20:11 ` Dave Jones
2005-09-29 21:14 ` Linus Torvalds
2005-09-29 21:26 ` Linus Torvalds
2005-09-29 21:33 ` Dave Jones
2005-09-29 21:55 ` Linus Torvalds
2005-09-29 22:12 ` Anton Altaparmakov
2005-09-29 22:25 ` Linus Torvalds
2005-09-29 22:32 ` Anton Altaparmakov
2005-09-29 23:19 ` Junio C Hamano
2005-09-30 12:22 ` Johannes Schindelin
2005-09-29 23:17 ` Horst von Brand
2005-09-30 0:47 ` Linus Torvalds
2005-09-30 1:54 ` Junio C Hamano
2005-09-30 2:36 ` Linus Torvalds
2005-10-01 0:10 ` Linus Torvalds
2005-10-01 1:58 ` Horst von Brand
2005-10-03 1:03 ` Linus Torvalds
2005-09-29 21:33 ` Elfyn McBratney
2005-09-29 21:35 ` Linus Torvalds
2005-09-29 21:40 ` Dave Jones
2005-09-29 20:15 ` Jeff Garzik
2005-09-29 21:04 ` Junio C Hamano
2005-09-30 11:15 ` Jeff Garzik
2005-09-30 11:55 ` Junio C Hamano
2005-09-30 14:11 ` Jeff Garzik [this message]
2005-10-02 8:47 ` Junio C Hamano
2005-09-30 18:14 ` Linus Torvalds
2005-10-01 7:36 ` Junio C Hamano
2005-09-30 12:02 ` Oliver Neukum
2005-09-30 13:58 ` Jeff Garzik
2005-09-30 15:10 ` Alberto Patino
2005-09-30 12:07 ` Erik Mouw
2005-09-30 14:08 ` Jeff Garzik
2005-09-30 18:13 ` Horst von Brand
2005-10-01 0:17 ` Jeff Garzik
2005-09-30 22:52 ` Francois Romieu
2005-09-29 21:23 ` Chuck Lever
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=433D477A.4010009@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).