From: Daniel Johnson <computerdruid@gmail.com>
To: nolan.ring@emc.com
Cc: git@vger.kernel.org
Subject: Re: svn2git question: Build directory inserted at top level?
Date: Wed, 15 Sep 2010 13:44:03 -0400 [thread overview]
Message-ID: <201009151344.17066.ComputerDruid@gmail.com> (raw)
In-Reply-To: <4E10ACF241081344B9702AA8C6440440C5B13F2162@MX01A.corp.emc.com>
[-- Attachment #1: Type: Text/Plain, Size: 903 bytes --]
Sidenote: You shouldn't reply to unrelated messages when starting a new
thread. In my mail client this shows up as a reply to "git log --pretty=format
joins lines in the subject of commit message" which doesn't seem to have
anything to do with your question.
On Wednesday 15 September 2010 09:47:42 nolan.ring@emc.com wrote:
> When I include the branches in the conversion I get a Build directory at
> the top level and then the usual directory structure of the repo. Where
> is the Build dir coming from? Is svn2git doing that? Or is it finding
> that somewhere somehow in the repo?
>
> buildadm@suse-s11:/work/POCcs> ls
> Build
> buildadm@suse-s11:/work/POCcs/Build> ls
> Automation build_cs_rpm.pl ControlStation depends.properties
Assuming the files are tracked by git, you might want to try running "git log
-- $filename" over them to see which commits touched them.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-15 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 12:55 git log --pretty=format joins lines in the subject of commit message Kirill Likhodedov
2010-09-15 13:01 ` Ævar Arnfjörð Bjarmason
2010-09-17 11:56 ` Kirill Likhodedov
2010-09-17 14:55 ` Jeff King
2010-09-15 13:47 ` svn2git question: Build directory inserted at top level? nolan.ring
2010-09-15 17:44 ` Daniel Johnson [this message]
2010-09-15 18:09 ` Torgny Nyblom
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=201009151344.17066.ComputerDruid@gmail.com \
--to=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=nolan.ring@emc.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).