From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Lars Schneider <larsxschneider@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Script to rebase branches
Date: Tue, 9 May 2017 12:50:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1705091244420.146734@virtualbox> (raw)
In-Reply-To: <20170509040943.j3n5li7fapiuvgbj@sigill.intra.peff.net>
Hi Peff,
On Tue, 9 May 2017, Jeff King wrote:
> On Sat, May 06, 2017 at 12:23:32PM +0200, Lars Schneider wrote:
>
> > I am about to write a bash/sh script that helps me to rebase a bunch of
> > branches (e.g. select branches based on prefix, conflict resolution/
> > rerere support, ...).
> >
> > I wonder if anyone has such a script already and is willing to share it.
>
> This is what I use:
>
> https://github.com/peff/git/blob/meta/rebase
>
> There's no documentation in the script, but the commit message in its
> history should give a good sense of what each part does.
That requires Meta/ to be checked out and up-to-date. I'd bet there are
exactly two people who fall into that category.
Also, I see that you do not use worktrees. Otherwise your script would
fail.
When I still hoped to be able to get the rebase--helper related topic
branches in by August last year, I had grandiose plans to teach the
sequencer not only to perform the Git garden shears' trick (i.e. recreate
merges), but also to optionally update local branches corresponding to the
merge commits, including updates to the worktrees that checked them out
(if any).
Maybe I'll still get around to do this, some time this year. And it'll
probably hit git.git by mid next year ;-)
Ciao,
Dscho
next prev parent reply other threads:[~2017-05-09 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 10:23 Script to rebase branches Lars Schneider
2017-05-06 17:14 ` Dennis Kaarsemaker
2017-05-09 4:09 ` Jeff King
2017-05-09 10:50 ` Johannes Schindelin [this message]
2017-05-09 11:02 ` Jeff King
2017-05-09 12:32 ` Johannes Schindelin
2017-05-10 4:46 ` Jeff King
2017-05-09 22:47 ` Junio C Hamano
2017-05-10 4:36 ` 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=alpine.DEB.2.21.1.1705091244420.146734@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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