mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michele Locati <>
To: Johannes Schindelin <>
Subject: Re: [PATCH v2] filter-branch: use printf instead of echo -e
Date: Thu, 22 Mar 2018 14:40:21 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <nycvar.QRO.>

Il 21/03/2018 22:50, Johannes Schindelin ha scritto:
> Hi Michele,
> On Mon, 19 Mar 2018, Michele Locati wrote:
>> [...]
>> -- 
> Yaaaaay!
> Out of curiosity: did the file help that was recently
> turned into a guide how to contribute to Git (for Windows) by Derrick
> Stolee?

Well, no. Here's what led me here...

The people behind the concrete5 CMS asked support for improving the 
following procedure:

concrete5 is stored in
In order to make it installable with Composer (a PHP package manager), 
we need to extract its "/concrete" directory, and push the results to
We previously used "git filter-branch --all" with this script:

That script is executed every time someone pushes concrete5/concrete5, 
and it took very long time (3~5 minutes).

I noticed on the git-filter-branch manual page that there's a 
"--state-branch", and it seemed quite interesting.
So, I asked in how to use it, and the author of that 
feature (Ian Campbell) told me to look at some code he wrote.
So, I wrote
which wraps "git filter-branch --filter-state", and it's used in
(it not yet in production: Korvin wants to be sure everything works well 
before adopting it)
The time required for the operation dropped from 3~5 minutes to ~10 
seconds ;)

While writing that script, I noticed a couple of things that could be 
improved in "git-filter-branch", so I submitted
(so that the script could run without problems if there's nothing to do)
(so that  --filter-state could be used on Mac and other non-Linux systems).
How did I learn how to submit to git? I searched for "git src", landed 
on, read Documentation/SubmittingPatches and 
used git send-email.

And yes, all that on Windows (and WSL).

> Ciao,
> Johannes



  reply	other threads:[~2018-03-22 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 14:49 [PATCH] filter-branch: use printf instead of echo -e Michele Locati
2018-03-19 15:39 ` CB Bailey
2018-03-20  4:22   ` Jeff King
2018-03-20  9:53     ` Ian Campbell
2018-03-20 10:21       ` Michele Locati
2018-03-19 15:52 ` [PATCH v2] " Michele Locati
2018-03-19 18:00   ` Junio C Hamano
2018-03-21 21:50   ` Johannes Schindelin
2018-03-22 13:40     ` Michele Locati [this message]
2018-03-23  9:35       ` Johannes Schindelin

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).