From: Johannes Sixt <j.sixt@viscovery.net>
To: shawn wilson <ag4ve.us@gmail.com>
Cc: Phil Hord <phil.hord@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Repo with only one file
Date: Fri, 09 Aug 2013 12:32:38 +0200 [thread overview]
Message-ID: <5204C546.1030502@viscovery.net> (raw)
In-Reply-To: <CAH_OBifYFyVVo_OEfniWJE=0peX+UPLkRznqyQzvO4gGGLu_tQ@mail.gmail.com>
Am 8/9/2013 12:03, schrieb shawn wilson:
> The question still stands though - why is that unassociated commit left there?
Because your command did not remove it. filter-branch does not know that
it is "unassociated" when you ask it to follow all commits beginning at
HEAD. But when you say 'HEAD -- webban.pl', you ask it to follow only
commits that touch webban.pl, which automatically skips that commit.
-- Hannes
next prev parent reply other threads:[~2013-08-09 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:24 Repo with only one file shawn wilson
2013-08-07 10:43 ` Johannes Sixt
2013-08-07 21:07 ` shawn wilson
2013-08-08 21:11 ` Phil Hord
2013-08-09 6:25 ` Johannes Sixt
2013-08-09 6:33 ` shawn wilson
2013-08-09 6:50 ` Johannes Sixt
2013-08-09 10:03 ` shawn wilson
2013-08-09 10:32 ` Johannes Sixt [this message]
2013-08-09 21:54 ` shawn wilson
2013-08-09 15:00 ` Phil Hord
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=5204C546.1030502@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=ag4ve.us@gmail.com \
--cc=git@vger.kernel.org \
--cc=phil.hord@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).