Page MenuHomeDevCentral

Footer
ClosedPublic

Authored by dereckson on Nov 13 2015, 19:43.
Referenced Files
Unknown Object (File)
Sun, Dec 15, 21:27
Unknown Object (File)
Wed, Dec 4, 04:23
Unknown Object (File)
Wed, Nov 27, 15:43
Unknown Object (File)
Sat, Nov 23, 18:26
Unknown Object (File)
Nov 16 2024, 02:49
Unknown Object (File)
Nov 16 2024, 00:47
Unknown Object (File)
Nov 11 2024, 14:16
Unknown Object (File)
Nov 7 2024, 21:33

Details

Summary

Add a footer forked from the Databases one to respect the Nasqueron style.

  • Second column: links to DevCentral, GitHub, Docker Hub & IRC
  • Third column: licensing information
  • Poem fragment: “And therefore one could, if one was sufficiently hardy, and adequately proof against the water pressure, make one's way down.”

Diff Detail

Repository
rDOCKERWWW Docker images website
Lint
Lint Skipped
Unit
No Test Coverage
Branch
footer
Build Status
Buildable 72
Build 72: arc lint + arc unit

Event Timeline

dereckson retitled this revision from to Footer.
dereckson updated this object.
dereckson edited the test plan for this revision. (Show Details)

Needs rebase.

Sandlayth edited edge metadata.
This revision is now accepted and ready to land.Nov 17 2015, 05:42
This revision was automatically updated to reflect the committed changes.

Footer is unreadable. Choose another color than white.

This revision is now accepted and ready to land.Nov 17 2015, 08:49
Sandlayth requested changes to this revision.Nov 17 2015, 08:50
Sandlayth edited edge metadata.
This revision now requires changes to proceed.Nov 17 2015, 08:50
dereckson added a reviewer: dereckson.
In D56#1147, @Kaliiixx wrote:

Footer is unreadable. Choose another color than white.

Revision has been merged to repository, as rDOCKERWWW4385a00791181ac6390ff7aaf8320b909d9b9341.

Once landed, further changes require a new commit to preserve the integrity of the public repository.

What do if a landed revision requires further work?

You can in such situation:

  • fill a bug
  • let a comment in Audit, the post-commit review

If a bug has been introduced by the commit, add to the bug you filled the Regression tag.

What do if an emergency occurs?

Now, sometimes, in dire emergency, we also can in such situations do this revert the change.

For that, create a revision with a revert patch (Git could do that):

git revert
arc diff

Well actually, it will be more:

git checkout master
git pull
git revert
arc diff

Then, add as reviewer the person submitting the patch.

If not responsive, and if nobody else answers, this is a case where self-merge is socially allowed.

Sandlayth edited edge metadata.

Understood.

This revision is now accepted and ready to land.Nov 17 2015, 21:04

Revision manually marked as closed through a SQL query.

UPDATE differential_revision SET status = 3 WHERE ID = 56;