Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

58

This is niche use case IMO.

JBRWilkinson
– JBRWilkinson

2012-03-29 22:30:19 +00:00
Commented Mar 29, 2012 at 22:30
18

But interesting nevertheless.

Jonathan
– Jonathan

2012-03-30 11:30:48 +00:00
Commented Mar 30, 2012 at 11:30
13

You can have semicolon at the end on a new line indented as the starting line. Then you copy and reorder things as you wish. This also closes the chain nicely.

Nux
– Nux

2013-05-11 17:38:33 +00:00
Commented May 11, 2013 at 17:38
25

Is it just me who wonders why anyone would care how neat the diffs of their commits look? as a general rule, people read code, not diffs.

Jules
– Jules

2014-12-03 12:06:13 +00:00
Commented Dec 3, 2014 at 12:06
20

@Jules, cleaner diffs mean merges are more likely to succeed.

joeytwiddle
– joeytwiddle

2016-02-14 06:09:39 +00:00
Commented Feb 14, 2016 at 6:09

| Show 5 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »