From: Enrico Weigelt <enrico.weigelt@vnc.biz>
To: Matt McHenry <mmchenry@carnegielearning.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn with ignore-paths misses/skips some revisions during fetch
Date: Sat, 10 Nov 2012 08:57:59 +0100 (CET) [thread overview]
Message-ID: <be90fa6b-3927-47cb-9306-6dbb7bac2c04@zcs> (raw)
In-Reply-To: <D377A9280DB18546A2471214D5CBB0E9054C25E071@exchdb01>
> The problem is that the 'ignore-paths' approach sometimes
> misses commits during a fetch, and then at some later time
> will "realize" it and squash those changes onto some other,
> unrelated commit. (I've never seen this happen with the
> per-subdir 'fetch' approach.) Here are three commits in
> SVN:
Could it be that certain files spent parts of their historical lifetime
inside the ignored paths ?
cu
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59
enrico.weigelt@vnc.biz; www.vnc.de
next prev parent reply other threads:[~2012-11-10 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 13:50 git-svn with ignore-paths misses/skips some revisions during fetch McHenry, Matt
2012-11-10 7:57 ` Enrico Weigelt [this message]
2012-11-12 15:00 ` McHenry, Matt
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=be90fa6b-3927-47cb-9306-6dbb7bac2c04@zcs \
--to=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
--cc=mmchenry@carnegielearning.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