Jump to content

Talk:Firozpur

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Spelling

[edit]

Before changing the spelling of Firozpur to Ferozpur or any other variant, please read WP:COMMONNAME. If you still consider that the change is justified and then you will need to request a move since we cannot have an article containing one spelling but under a title with another spelling. Thanks. - Sitush (talk) 08:44, 1 May 2014 (UTC)[reply]

I have opened a centralised discussion regarding possible renaming of this article. Please feel free to comment at Wikipedia talk:Noticeboard for India-related topics#Centralised naming discussion - Firozpur.2FFerozpur. Thanks. - Sitush (talk) 10:55, 10 September 2014 (UTC)[reply]

History behind the name of Firozpur

[edit]

Firoz Khan was a very close friend of Mughal Emperor Humayon who came from Afghanistan with Humayon in 1572. After his death, Mughal Emperor Humayon named the district after his friend's name Firozpur. — Preceding unsigned comment added by Haiderism (talkcontribs) 19:50, 21 March 2019 (UTC)[reply]

Unwarranted reversion

[edit]

To editor Dhruv edits: There was no earthly reason for you to revert this edit of mine, describing it as an "unconstructive edit" in your edit summary. I noticed that you later restored my changes, but without any explanation (i.e. no ES at all). I would very much appreciate an explanation. (If it was in error—which of course can happen to anyone—it would have been nice to see some indication of that.) Thank you AukusRuckus (talk) 14:42, 14 February 2022 (UTC)[reply]

It was incidental revert due to series of unconstructive IP edits. Dhruv edits (talk) 14:49, 14 February 2022 (UTC)[reply]
@Dhruv edits: [Wow]. Well, as it was just "incidental", I guess that means I shouldn't be perturbed by your actions? That is your full measure of concern or courtesy for lumping in a well-intentioned editor with an "unconstructive edits" edit summary? Really? Wow, just ... AukusRuckus (talk) 14:58, 14 February 2022 (UTC)[reply]