What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 130 Stack Exchange communities.

SQLite CSV Import question is updated as per the suggestions.
I am wondering why is it not being reopened.

share|improve this question

closed as too localized by animuson, hims056, Tim Post Mar 1 '13 at 6:46

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Did you flag for reopen? –  hims056 Mar 1 '13 at 4:43
    
I am under the impression that flagging adds more negativeness to question than asking for reopen!! –  Seenu Mar 1 '13 at 4:46
1  
No. If you have edited a question and you think the question is appropriate for Stack Overflow (after editing), then flagging is the best way to reopen your question. –  hims056 Mar 1 '13 at 4:49
3  
Nice job on editing it into shape! In the future, you can just flag for a question to be re-opened. This ensures that a moderator has a look at it if the community has not already voted to reopen it for you. The flag does not in any way cast a negative light on your account. –  Tim Post Mar 1 '13 at 5:10
    
@TimPost, Just wondering if it is the same for closing an exact duplicate if community is not doing the same. I had voted to close this question which is an exact duplicate of this but there was no action on that. Is flagging the right option there also? Or will it be rejected since I have voting privilege to close it? –  iDev Mar 1 '13 at 6:22
    
@ACB You can flag, if the questions are at least similar and the moderator could see how you would think it's a duplicate the flag should generally be validated. It doesn't mean the specific action will be taken, though - but no harm in raising it. –  Tim Post Mar 1 '13 at 6:45
    
@TimPost, Thanks. I have flagged it. Both questions are talking about the same problem(about a new warning in Xcode4.6 "Used As Name of the previous parameter rather than as part of selector") and the solution is the same for both. This can be seen from the title of both questions itself. –  iDev Mar 1 '13 at 7:03

1 Answer 1

The question has now been reopened.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .