From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Lars Schneider <larsxschneider@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Script to rebase branches
Date: Sat, 06 May 2017 19:14:07 +0200 [thread overview]
Message-ID: <1494090847.24179.7.camel@kaarsemaker.net> (raw)
In-Reply-To: <8D018370-79F9-450F-97AF-31EF4C95BA44@gmail.com>
On Sat, 2017-05-06 at 12:23 +0200, Lars Schneider wrote:
> Hi,
>
> 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.
Dscho's git garden shears perhaps?
https://github.com/git-for-windows/build-extra/blob/master/shears.sh
D.
next prev parent reply other threads:[~2017-05-06 17:14 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 [this message]
2017-05-09 4:09 ` Jeff King
2017-05-09 10:50 ` Johannes Schindelin
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=1494090847.24179.7.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=larsxschneider@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;
as well as URLs for NNTP newsgroup(s).