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.

+1 except I don't know what deep and shallow really means in this context, perhaps you could expand on those terms a little?

Michael Durrant
– Michael Durrant

2015-04-14 11:55:32 +00:00
Commented Apr 14, 2015 at 11:55
Thinks of branches making a tree. They may come out the trunk or another branch. Shallow means that the number of branching step between the branch and the trunk is small, deep means that the number of branching step is important. What small and important is is mostly relative, but I've seen schemes for which each new releases was a step further than the previous one from the trunk. If you are using a flat namespace, that's not so bad. If the namespace is hierarchical (clearcase, CVS, RCS, Perforce can be used in such a way as well), you get longer and longer names.

AProgrammer
– AProgrammer

2015-04-14 12:34:16 +00:00
Commented Apr 14, 2015 at 12:34

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 »