From: Christopher Tiwald <christiwald@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] update-index: add --clear option
Date: Tue, 17 Apr 2012 14:36:49 -0400 [thread overview]
Message-ID: <CAHiigudcsEqaZwv7MpRVEw-5V60VJ7zemuh4u902vvhrAsRJGQ@mail.gmail.com> (raw)
In-Reply-To: <20120416214855.GM12860@gmail.com>
On Mon, Apr 16, 2012 at 5:48 PM, Christopher Tiwald
<christiwald@gmail.com> wrote:
> At the very least I can give this patch series a go this evening. I'm in
> the process of combining 40 highly-intertwined, nested repositories into
> one, and should be able to test it under the conditions outlined in the
> updated example.
This worked great for me, at least in the case of adding trees to
subdirectories.
Fwiw, I found the newer, patched example a little easier to parse, but
I also had
spent a while figuring out what the original version did.
--
Christopher Tiwald
next prev parent reply other threads:[~2012-04-17 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 16:00 Filter-branch's "move tree to subdirectory" example fails with BSD sed? Christopher Tiwald
2012-04-14 19:25 ` Johannes Sixt
2012-04-16 15:27 ` Jeff King
2012-04-16 16:02 ` [RFC/PATCH 1/2] update-index: add --clear option Jeff King
2012-04-16 21:48 ` Christopher Tiwald
2012-04-17 18:36 ` Christopher Tiwald [this message]
2012-04-16 16:03 ` [RFC/PATCH 2/2] docs/filter-branch: clean up newsubdir example Jeff King
2012-04-16 17:03 ` Filter-branch's "move tree to subdirectory" example fails with BSD sed? Junio C Hamano
2012-04-16 17:13 ` 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=CAHiigudcsEqaZwv7MpRVEw-5V60VJ7zemuh4u902vvhrAsRJGQ@mail.gmail.com \
--to=christiwald@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--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;
as well as URLs for NNTP newsgroup(s).