git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: svn2git question: Build directory inserted at top level?

From
Daniel Johnson <computerdruid@gmail.com>
Date
Sep 15, 2010, 17:44 UTC
Message-ID
<201009151344.17066.ComputerDruid@gmail.com>
In-Reply-To
<4E10ACF241081344B9702AA8C6440440C5B13F2162@MX01A.corp.emc.com>
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:
Show 9 quoted lines
> 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.

Previous: nolan.ring@emc.comNext: Torgny Nyblom
Message 6 of 7 in “git log --pretty=format joins lines in the subject of commit message”
  1. Kirill LikhodedovSep 15, 2010
  2. Ævar Arnfjörð BjarmasonSep 15, 2010
  3. Kirill LikhodedovSep 17, 2010
  4. Jeff KingSep 17, 2010
  5. svn2git question: Build directory inserted at top level?nolan.ring@emc.com, Sep 15, 2010
  6. Daniel JohnsonSep 15, 2010
  7. Torgny NyblomSep 15, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.