| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| .gitted | ||
| my-submodule @ efad0b11 | ||
| .gitmodules | ||
| asparagus.txt | ||
| beef.txt | ||
| bouilli.txt | ||
| gravy.txt | ||
| oyster.txt | ||
| veal.txt |
An untracked file in a submodule should not prevent a rebase from starting. Even if the submodule's SHA is changed, and that file would conflict with a new tracked file, it's still OK to start the rebase and discover the conflict later. Signed-off-by: David Turner <dturner@twosigma.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| .gitted | Loading commit data... | |
| my-submodule @ efad0b11 | ||
| .gitmodules | Loading commit data... | |
| asparagus.txt | Loading commit data... | |
| beef.txt | Loading commit data... | |
| bouilli.txt | Loading commit data... | |
| gravy.txt | Loading commit data... | |
| oyster.txt | Loading commit data... | |
| veal.txt | Loading commit data... |