From: Eric Sunshine <sunshine@sunshineco.com>
To: Ilya Basin <basinilya@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>,
Ray Chen <rchen@cs.umd.edu>, Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH 5/5] git-svn: fix empty dir tracking in branches
Date: Tue, 30 Apr 2013 23:25:02 -0400 [thread overview]
Message-ID: <CAPig+cT4657Amv2E5yj3K3cv-FYXSSm=-=CE_apXomp4QvSiEw@mail.gmail.com> (raw)
In-Reply-To: <51800471.6905700a.65c8.00b9@mx.google.com>
On Tue, Apr 30, 2013 at 1:38 PM, Ilya Basin <basinilya@gmail.com> wrote:
> - When creating a tag or branch from a subdir, a disjoint branch is
> created. Then git-svn re-imports the commits using this dir as strip
> path.
>
> During this re-import the variable %added_placeholder is not up to
> date. Because the branch is disjoint, this variable should be empty
> in the beginning, but it's not. Because of that git-svn tries to
> delete non-existent .gitignore files and dies.
>
> - When creating a tag or branch from a subdir, the strip path is e.g.
> "trunk/module", but change_dir_prop() can be called with just
> "trunk". This breaks tracking of placeholder files, because it
> relise on the hash {dir_prop}, filled in change_dir_prop().
s/relise/relies/
>
> - When creating a normal tag or branch, git-svn creates a normal
> branch without reimport, but the placeholder files in the new
> branch are not added to %added_placeholder.
>
> This patch does 3 things:
>
> - It makes git-svn store paths in %added_placeholder already
> translated from "trunk/subdir/" to "tags/subdir_1.0/" during
> reimport.
>
> - When strip path is "trunk/subdir", don't add "trunk" to {dir_prop}
> in change_dir_prop().
>
> - When a normal branch is created, it takes entries in
> %added_placeholder belonging to the source branch, translates them
> to target branch and adds them to %added_placeholder.
prev parent reply other threads:[~2013-05-01 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 17:38 [PATCH 5/5] git-svn: fix empty dir tracking in branches Ilya Basin
2013-05-01 3:25 ` Eric Sunshine [this message]
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='CAPig+cT4657Amv2E5yj3K3cv-FYXSSm=-=CE_apXomp4QvSiEw@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=basinilya@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=rchen@cs.umd.edu \
/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).