| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
|
|
|
|
|
|
| |
Similar to Git, scripts including the dispatcher sib are grouped into
libexec/sib-core, and symlinks are created in bin/sib. Additionally,
libexec/sib-core is added to the PATH when executing any script inside
sib. I don't really see any downside to adding to the PATH and loading
the script. It's clear.
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
| |
Signed-off-by: Hee-Suk Kim <[email protected]>
|
| |
|
|
|
|
|
| |
The problem was that the HEAD update by -p depended on user input, so
I just branched at that point.
Signed-off-by: Hee-Suk Kim <[email protected]>
|
|
|
Excluded receiving the prompt as an argument because it increases code
complexity. Besides, inputting from stdin is more convenient in the
first place... Since it is difficult to distinguish between input
blocking and API call blocking, print a warning message in that case.
Signed-off-by: Hee-Suk Kim <[email protected]>
|