All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Christopher Tiwald <christiwald@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Filter-branch's "move tree to subdirectory" example fails with BSD sed?
Date: Sat, 14 Apr 2012 21:25:05 +0200	[thread overview]
Message-ID: <4F89CF11.7060309@kdbg.org> (raw)
In-Reply-To: <20120414160028.GD1012@gmail.com>

Am 14.04.2012 18:00, schrieb Christopher Tiwald:
> The "Move tree to subdirectory" example in the 'git filter-branch'
> manpage fails on Mac OSX 10.7.3, but succeeds on Ubuntu 10.04.

> git init "test"
> cd "test"
> mkdir -p subdirA/subdirB
> echo content > subdirA/subdirB/file
> git add .
> git commit -m "initial commit"
> git ls-files -s | sed "s-\t\"*-&newsubdir/-"
> 
> On Mac 10.7.3 the final command outputs:
> 100644 d95f3ad14dee633a758d2e331151e950dd13e4ed 0	subdirA/subdirB/file
> 
> On Ubuntu 10.04:
> 100644 d95f3ad14dee633a758d2e331151e950dd13e4ed 0	newsubdir/subdirA/subdirB/file

Perhaps a literal TAB instead of \t makes the example work?

It would be difficult, though, to write this down in the manual in an
unambiguous way.

-- Hannes

  reply	other threads:[~2012-04-14 19:25 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 [this message]
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
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=4F89CF11.7060309@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=christiwald@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.