Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000207Rosetta[All Projects] Bad Codingpublic2013-03-13 11:542013-03-16 10:37
Reportersmlewis 
Assigned Tosmlewis 
PrioritynoneSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Fixed in Version 
Summary0000207: ERRASER leaves un-ignored .pyc files
Descriptionrosetta> git status
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# rosetta_tools/ERRASER/erraser_option.pyc
# rosetta_tools/ERRASER/erraser_util.pyc
# rosetta_tools/ERRASER/erraser_wrapper.pyc
# rosetta_tools/ERRASER/measure_params.pyc
nothing added to commit but untracked files present (use "git add" to track)
TagsNo tags attached.
Application(s) AffectedSVN / git issue
Command Line UsedSVN / git issue
Developer OptionsConfirmed As Bug
Fixed in SVN Version54253
Attached Files

- Relationships
parent of 0000215new top-level .gitignore after we move to git 
related to 0000209resolvedsmlewis temp files committed to trunk 
Not all the children of this issue are yet resolved or closed.

-  Notes
(0000165)
smlewis (Administrator)
2013-03-13 12:07

rosetta_tools had no .gitignore...fixed in my local git but this needs to be crosschecked against svn
(0000166)
rmoretti (Attentive Developer)
2013-03-13 12:56

This somewhat raises the question of where .gitignore should be located. Right now it's in rosetta_source (with a few extra ones scattered around). Should that be moved up one directory to rosetta/ proper to apply to all the directories?

This would not only fix the .pyc issues, but would also apply to text editor temporary/backup files and Mac-like shell resouce files (.DStore, etc.) in the non-source directory.
(0000169)
smlewis (Administrator)
2013-03-13 13:04

I think a toplevel .gitignore is appropriate in the long term, but it should probably wait until after we move the whole community to git - I think ultimately one will cover source/database/tests, and a separate one each for demos and tools (given my understanding of the git split plan)
(0000176)
smlewis (Administrator)
2013-03-16 10:32

I will file a separate child bug for the general case

- Issue History
Date Modified Username Field Change
2013-03-13 11:54 smlewis New Issue
2013-03-13 11:54 smlewis Status new => assigned
2013-03-13 11:54 smlewis Assigned To => smlewis
2013-03-13 12:07 smlewis Note Added: 0000165
2013-03-13 12:56 rmoretti Note Added: 0000166
2013-03-13 13:00 rmoretti Relationship added related to 0000209
2013-03-13 13:04 smlewis Note Added: 0000169
2013-03-16 10:32 smlewis Fixed in SVN Version => 54253
2013-03-16 10:32 smlewis Note Added: 0000176
2013-03-16 10:32 smlewis Status assigned => resolved
2013-03-16 10:32 smlewis Resolution open => fixed
2013-03-16 10:37 smlewis Relationship added parent of 0000215


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker