From: "Александр Овчинников" <proff@proff.email>
To: git@vger.kernel.org
Subject: may be bug in svn fetch no-follow-parent
Date: Mon, 20 Jun 2016 10:36:28 +0300 [thread overview]
Message-ID: <4094761466408188@web24o.yandex.ru> (raw)
Why git svn fetch try to handle mergeinfo changes when no-follow-parent is enabled?
Git try to follow parents regardless of this option value.
If branch created without this option then git will follow parent succesfully
If branch created with this option then git try to follow and fail with "cannot find common ancestor" error
If branch does not exists (ignored) then git try to follow and fail with "couldn't find revmap" error. It is very long operation
next reply other threads:[~2016-06-20 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 7:36 Александр Овчинников [this message]
2016-06-20 21:52 ` may be bug in svn fetch no-follow-parent Eric Wong
[not found] ` <2518541466501215@web27h.yandex.ru>
2016-06-22 22:58 ` Eric Wong
2016-06-24 10:57 ` Александр Овчинников
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4094761466408188@web24o.yandex.ru \
--to=proff@proff.email \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).