Timeline for tar with relative paths
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 20, 2020 at 9:41 | history | suggested | Chris Tang | CC BY-SA 4.0 |
reformat the content to increase readability
|
| Mar 20, 2020 at 8:16 | review | Suggested edits | |||
| S Mar 20, 2020 at 9:41 | |||||
| Aug 6, 2019 at 12:52 | review | Suggested edits | |||
| Aug 6, 2019 at 17:16 | |||||
| Oct 8, 2015 at 12:09 | comment | added | Piotr Dobrogost |
So what? Both instances of ~ are expanded and the whole invocation is not working as expected only because the last argument in case of using -C should have been given as relative path but instead is given as absolute path. Using ~ here does not matter at all.
|
|
| Oct 8, 2015 at 10:43 | comment | added | symcbean | No - look at the original question - the last argument is an absolute path. | |
| Oct 8, 2015 at 8:49 | comment | added | Piotr Dobrogost |
Explanation is wrong. It doesn't matter here that ~ is expanded by shell. What matters is that -C changes current working directory as explained in anwer by Lekensteyn.
|
|
| Oct 19, 2011 at 10:32 | vote | accept | Mert Nuhoglu | ||
| Oct 18, 2011 at 11:07 | history | answered | symcbean | CC BY-SA 3.0 |