From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Chanters <david.chanters@googlemail.com>, git@vger.kernel.org
Subject: Re: A note from the maintainer: Follow-up questions (MaintNotes)
Date: Mon, 31 Aug 2009 22:55:04 -0400 [thread overview]
Message-ID: <20090901025504.GA23589@coredump.intra.peff.net> (raw)
In-Reply-To: <7v8wgzla02.fsf@alter.siamese.dyndns.org>
On Mon, Aug 31, 2009 at 06:38:37PM -0700, Junio C Hamano wrote:
> a71f64a Merge branch 'pk/import-dirs' into pu
> ce6cd39 Merge branch 'jh/cvs-helper' into pu
> ...
> 2178d02 Merge branch 'jc/log-tz' into pu
> ...
> 927d129 Merge branch 'lt/approxidate' into jch
> 35ada54 Merge branch 'tr/reset-checkout-patch' into jch
> d82f86c Merge branch 'db/vcs-helper' (early part) into jch
>
> So if you for example happen to be interested in jc/log-tz topic,
> you would do something like:
>
> $ git checkout -b jc/log-tz 2178d02^2
> $ git log -p master..
>
> to check out, and view what changes the topic introduces.
Another alternative: Thomas Rast wrote a handy script called
'git-resurrect' which does this for you. It's carried in the contrib/
section right now. I used it just the other day to pull out the
lt/approxidate topic branch, which I then built some follow-up patches
for. Usage is something like:
# contrib scripts aren't installed by "make install",
# so put it somewhere in your PATH
$ cp contrib/git-resurrect.sh ~/bin/git-resurrect
$ git resurrect -m lt/approxidate
** Candidates for lt/approxidate **
931e8e2 [22 hours ago] fix approxidate parsing of relative months and years
** Restoring lt/approxidate to 931e8e2 fix approxidate parsing of relative months and years
-Peff
next prev parent reply other threads:[~2009-09-01 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 22:19 A note from the maintainer: Follow-up questions (MaintNotes) David Chanters
2009-08-31 8:05 ` Andreas Ericsson
2009-09-01 1:38 ` Junio C Hamano
2009-09-01 2:55 ` Jeff King [this message]
2009-09-01 16:58 ` David Chanters
2009-09-01 19:09 ` Junio C Hamano
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=20090901025504.GA23589@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=david.chanters@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).