From: Johannes Sixt <j.sixt@viscovery.net>
To: David Tweed <david.tweed@gmail.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: Understanding git filter-branch --subdirectory-filter behaviour
Date: Wed, 21 May 2008 08:26:03 +0200 [thread overview]
Message-ID: <4833C07B.3060004@viscovery.net> (raw)
In-Reply-To: <e1dab3980805201311m3cbde4f2id8c3493a25745238@mail.gmail.com>
David Tweed schrieb:
> $ git filter-branch --subdirectory-filter WRITING/ HEAD
> Rewrite 42f24be8d8198738134a19471697b39359199fa3 (351/351)
> Ref 'refs/heads/master' was rewritten
>
> $ git rev-list HEAD | wc
> 55 55 2255
>
...
>
> Digging a little into the shell-script I find the list of commits is
> generated with
>
> git rev-list --reverse --topo-order --default HEAD --parents HEAD
> --full-history -- WRITING
>
> and (adding --pretty so I can easily read it) running this manually
> gives 351 entries and looks to contain the expected commits. So I'm
> confused what's happening?
That's difficult to tell without a peek at the repository.
Did you compare 'gitk HEAD' to 'gitk HEAD -- WRITING'? I'd expect the
latter to be a subset of the former. Note that with a path specified
"history simplification" happens, which means that you won't see as many
merges as when no path is specified.
-- Hannes
next prev parent reply other threads:[~2008-05-21 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 20:11 Understanding git filter-branch --subdirectory-filter behaviour David Tweed
2008-05-21 6:26 ` Johannes Sixt [this message]
2008-05-22 18:05 ` David Tweed
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=4833C07B.3060004@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=david.tweed@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.