Edit - Stack Overflow

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.

Rev

2

Since I was just squashing ~100 commits (for syncing svn branches via git-svn), this is far faster than interactively rebasing!
– sage
Commented Nov 3, 2015 at 20:34
2

Reading down, I see @Chris's comment, which is what I used to do (rebase --soft...) - too bad that stackoverflow is no longer putting the answer with hundreds of upvotes at the top...
– sage
Commented Nov 3, 2015 at 20:35
2

agree with you @sage, lets hope they might do it sometime in the future
– Sandesh Kumar
Commented Nov 3, 2015 at 20:51
This is the right way. Rebase approach is good, but should only be used for squash as a last resort solution.
– Axalix
Commented Mar 11, 2019 at 20:13
I'm getting everything up to date
– Jake Sylvestre
Commented Dec 6, 2020 at 16:33

Add a comment |

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 »

Collectives™ on Stack Overflow