Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PATCH] (4.6.1) Fixup homepage url #138

Closed
mc-butler opened this issue Jan 4, 2009 · 10 comments
Closed

[PATCH] (4.6.1) Fixup homepage url #138

mc-butler opened this issue Jan 4, 2009 · 10 comments
Assignees
Labels
area: core Issues not related to a specific subsystem prio: high Serious problem that could block progress ver: 4.6.1 Reproducible in version 4.6.1
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/138
Reporter Enrico.Weigelt@….local, metux IT service <weigelt@….de>
Keywords committed-master, committed-mc-4.6

This patch fixes the homepage url to http://www.midnight-commander.org/ in various locations

Committed mc-4.6: [315633e]
Committed master: [8c917bb]

Note

Original attachments:

@mc-butler
Copy link
Author

Changed by mc-butler (@mc-butler) on Jan 4, 2009 at 0:46 UTC

This message has 1 attachment(s)

@mc-butler
Copy link
Author

Changed by metux (@metux) on Jan 4, 2009 at 1:40 UTC (comment 2)

  • Summary changed from [PATCH] 4.6.1: Fixup homepage url to [PATCH] (4.6.1) Fixup homepage url
  • Milestone set to 4.6.2
  • Priority changed from major to critical
  • Description edited

@mc-butler
Copy link
Author

Changed by metux (@metux) on Jan 6, 2009 at 18:48 UTC (comment 3)

  • Keywords set to review

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Jan 9, 2009 at 1:04 UTC (comment 4)

  • Owner set to slavazanko
  • Status changed from new to accepted

for close this ticket, need to accept...

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Jan 9, 2009 at 1:05 UTC (comment 5)

  • Status changed from accepted to testing
  • Resolution set to duplicate

Duplicate #137

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Jan 9, 2009 at 1:06 UTC (comment 6)

  • Keywords review deleted

@mc-butler
Copy link
Author

Changed by Enrico Weigelt on Jan 9, 2009 at 15:50 UTC

Comment:

Duplicate #137

hmm, not completely ;-o
I've opened two tickets, one per branch. stable and current
need separate patches.

cu

@mc-butler
Copy link
Author

Changed by metux (@metux) on Jan 11, 2009 at 20:40 UTC (comment 8)

  • Keywords set to committed-master, committed-mc-4.6
  • Description edited

@mc-butler
Copy link
Author

Changed by winnie (@winnieXY) on Jan 13, 2009 at 21:51 UTC (comment 9)

  • Status changed from testing to closed

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Feb 20, 2025 at 15:39 UTC (comment 10)

  • Branch state set to no branch

Closed as duplicate of #137.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: high Serious problem that could block progress ver: 4.6.1 Reproducible in version 4.6.1
Development

No branches or pull requests

2 participants