From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Thomas Rast" <trast@student.ethz.ch>,
"Björn Gustavsson" <bgustavsson@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Johannes Sixt" <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2010, #05; Sun, 21)
Date: Mon, 22 Feb 2010 05:37:09 -0500 [thread overview]
Message-ID: <20100222103709.GA16531@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.1.00.1002221108100.20986@pacific.mpi-cbg.de>
On Mon, Feb 22, 2010 at 11:08:51AM +0100, Johannes Schindelin wrote:
> > You mean this one?
> >
> > http://permalink.gmane.org/gmane.comp.version-control.git/108330
>
> Yes, indeed. But it was applied, I just did not find it due to the name,
> which is not intuitive to this developer.
It is also slightly overkill if all you want to do is pull Junio's
topics from pu (I found myself always forgetting the right incantation
of command line options). The script posted by Björn is much shorter,
but recovers all topic branches. If you just want to pull one, I think:
#!/bin/sh
sha1=`git log --oneline --first-parent origin/pu |
grep -m 1 "Merge branch '$1'" |
cut -d ' ' -f1`
git branch ${2:-$1} $sha1^2
should work. Though I have not been using it very long myself, so it is
possible that it has bugs. :)
-Peff
next prev parent reply other threads:[~2010-02-22 10:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 0:19 What's cooking in git.git (Feb 2010, #05; Sun, 21) Junio C Hamano
2010-02-22 3:08 ` Larry D'Anna
2010-02-22 7:35 ` Johannes Sixt
2010-02-22 7:49 ` Junio C Hamano
2010-02-22 8:17 ` Björn Gustavsson
2010-02-22 8:37 ` Johannes Schindelin
2010-02-22 9:48 ` Thomas Rast
2010-02-22 10:01 ` Thomas Rast
2010-02-22 10:08 ` Johannes Schindelin
2010-02-22 10:37 ` Jeff King [this message]
2010-02-22 10:52 ` Jeff King
2010-02-22 20:21 ` Junio C Hamano
2010-02-23 0:53 ` Jeff King
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=20100222103709.GA16531@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=bgustavsson@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=trast@student.ethz.ch \
/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).