From: "Santi Béjar" <santi@agolina.net>
To: Frank Li <lznuaa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git log can not show history before rename
Date: Fri, 30 Jan 2009 13:49:34 +0100 [thread overview]
Message-ID: <adf1fd3d0901300449x7f6a2f5bq920068b46994c92e@mail.gmail.com> (raw)
In-Reply-To: <1976ea660901300429i6d9b3594m91222314c284d184@mail.gmail.com>
[Please, don't top post, and quote only what you are replying to]
2009/1/30 Frank Li <lznuaa@gmail.com>:
> Does it conflict with --parents?
> When I use --follow and --parents together, parents can't rewrite.
> without --follow, parent can rewrite.
I think there are no obvious reasons to conflict and they could work
together, but as Jakub just said, --follow is quite new and only works
well with simple history and simple cases.
Santi
next prev parent reply other threads:[~2009-01-30 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 11:23 Git log can not show history before rename Frank Li
2009-01-30 11:29 ` Santi Béjar
2009-01-30 12:25 ` Jakub Narebski
2009-01-30 12:29 ` Frank Li
2009-01-30 12:49 ` Santi Béjar [this message]
2009-01-30 21:52 ` Thomas Rast
2009-01-31 7:04 ` Jeff King
2009-01-30 17:17 ` Linus Torvalds
2009-01-30 17:23 ` Linus Torvalds
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=adf1fd3d0901300449x7f6a2f5bq920068b46994c92e@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@vger.kernel.org \
--cc=lznuaa@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).