In #1081308: Include "-u" option in new branch instructions, dww suggests In fact, I daresay we could consider adding sections at the bottoms of certain doc pages with "Already using Git 1.7? You can also..." wisdom.

The command in question actually was introduced in 1.7.0.9 which came out in December 2010, but I'm +1 to the idea of having a predictable location at the bottom of the docs for newer, innovative commands.

Comments

eliza411’s picture

Title: Include » Create a pattern for newer Git commands in the Git docs

fixing title

eliza411’s picture

Component: Placement/Navigation/Strucure » Correction/Clarification
Assigned: Unassigned » danmuzyka

How about we use the following:

Newer Git commands

If you're running Git x.x.x or later:
etc.

I put this in place at http://drupal.org/node/1066342

Then when it's time to update docs because newer versions are being included in distros, we can find all the references and Git instructions can get updated accordingly as well.

danmuzyka’s picture

Issue tags: +git phase 3

Makes sense. How should we go about doing this? Just add the new commands to the bottom whenever someone files an issue? I am not a Git expert so will not be the best person to proactively add this information to the documentation without specific guidance.

eliza411’s picture

Yeah, I'd say it'll end up happening in response to specific issues on the rare occasions the situation exists.

danmuzyka’s picture

Status: Active » Fixed

OK, cool, I will keep an eye out for issues people post and add them in this manner. Thanks for the heads up.

Status: Fixed » Closed (fixed)
Issue tags: -git, -git phase 3

Automatically closed -- issue fixed for 2 weeks with no activity.