From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: --first-parent plus path limiting
Date: Tue, 29 Jan 2008 01:11:35 -0800 [thread overview]
Message-ID: <7v63xdov20.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <479EEC3D.9030100@viscovery.net> (Johannes Sixt's message of "Tue, 29 Jan 2008 10:05:01 +0100")
Johannes Sixt <j.sixt@viscovery.net> writes:
> I was expecting that it works like "First follow the first-parent, and
> then simplify the history with respect to builtin-fetch.c."
If you first follow the first-parent, the result will by
definition not have any merges, so there is nothing left to
simplify. History simplification is about merge removal,
looking at all parents.
Removing commits from a single strand of pearls that do not
touch the specified pathspecs is called "--dense" (which is on
the default) and can be disabled with "--sparse".
So, no, it is not a matter of definition, as "first follow the
first-parent then simplify" does not make much sense.
next prev parent reply other threads:[~2008-01-29 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 8:29 --first-parent plus path limiting Johannes Sixt
2008-01-29 8:47 ` Junio C Hamano
2008-01-29 9:05 ` Johannes Sixt
2008-01-29 9:11 ` Junio C Hamano [this message]
2008-01-29 9:18 ` Johannes Sixt
2008-01-29 20:03 ` Junio C Hamano
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=7v63xdov20.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.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 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.