If I execute
mypath=`cygpath -w ../`
echo $mypath
I get
d:\unix\nextVersion\script
OK, d:\unix\nextVersion\script is the correct windows version of the path, but it is in absolute form. I would prefer it if cygpath left it in relative form, i.e.
echo $mypath
should output
..\
... (0 Replies)
forgive my ignorance.
I did a search of this sub-forum for "tar -xp" and variations on the same w\out success, so here goes...
Scenario:
filename.tar file.
Desired Task:
I want to be able to extract only files from the user's public_html folder (and all those under it as an option) from... (4 Replies)
Hi,
I have a file paths.txt with all the file paths. I want to tar everything in those paths to a file.
for example paths.txt contains
/data/extention
/logs/extension
/code/extenstion
Now I want to tar using command
tar cvf extention.tar path1 path2
where
path1 -> /data/extention... (2 Replies)
There is a file paths.txt with paths containing data for example
E:/<BUILD_NAME>/data/common
E:/<BUILD_NAME>/log/common
E:/<BUILD_NAME>/temp/common
E:/<BUILD_NAME>/code/common
While reading this file I want to replace the <BUILD_NAME> from a variable $BUILD in the following command:
tar... (1 Reply)
Hi Gurus,
I have a .tar file which required untar to the new location. I list the content with –tvf its listing the files which are inside the tar, when I am extracting he file from tar its working fine, however once I am trying to extract the file at the new location I am unable to do so. I... (11 Replies)
I create the tar file from / like so:
tar cEhf name.tar usr/us
And this creates the tar with the links intact. The problem is that this tar is going to be used for testing, so we want the links to point to the files in the tar. But when I extract the tar into /tmp, I get /tmp/usr/us/... as I... (2 Replies)
Can someone cofirm that I have got the paths correct here? :confused:
$PATH_TO_TMP_DIR='/tmp';
#$PATH_TO_TMP_DIR='home/tmp';
$PATH_TO_YOUR_IMG_DIR = '/temp_images';
#$PATH_TO_YOUR_IMG_DIR = 'home/public_html/Midwich/temp_images';
Thanks (1 Reply)
When I specify a directory by name the leading ./ is not shown:
$ find somedir/
somedir/a.bin
somedir/target/out.binBut when I specify current dir it adds the ./ to the beginning of each result:
$ find . | grep somedir
./somedir/a.bin
./somedir/target/out.binIs there any particular reason why... (2 Replies)
I am able to list all the filenames under a directory & its sub-directories except blent.tar on Linux
find "/tmp/" -type f | grep -v blent.tar | rev | cut -d '/' -f1 | rev
Desired Output:
THIRDPARTYLICENSEREADME.txt
javaws
libjavaplugin_oji.so
libjavaplugin_oji.so... (3 Replies)
Discussion started by: mohtashims
3 Replies
LEARN ABOUT CENTOS
git-tar-tree
GIT-TAR-TREE(1) Git Manual GIT-TAR-TREE(1)NAME
git-tar-tree - Create a tar archive of the files in the named tree object
SYNOPSIS
git tar-tree [--remote=<repo>] <tree-ish> [ <base> ]
DESCRIPTION
THIS COMMAND IS DEPRECATED. Use git archive with --format=tar option instead (and move the <base> argument to --prefix=base/).
Creates a tar archive containing the tree structure for the named tree. When <base> is specified it is added as a leading path to the files
in the generated tar archive.
git tar-tree behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used
as modification time of each file in the archive. In the latter case the commit time as recorded in the referenced commit object is used
instead. Additionally the commit ID is stored in a global extended pax header. It can be extracted using git get-tar-commit-id.
OPTIONS
<tree-ish>
The tree or commit to produce tar archive for. If it is the object name of a commit object.
<base>
Leading path to the files in the resulting tar archive.
--remote=<repo>
Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.
CONFIGURATION
tar.umask
This variable can be used to restrict the permission bits of tar archive entries. The default is 0002, which turns off the world write
bit. The special value "user" indicates that the archiving user's umask will be used instead. See umask(2) for details.
EXAMPLES
git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)
Create a tar archive that contains the contents of the latest commit on the current branch, and extracts it in /var/tmp/junk directory.
git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz
Create a tarball for v1.4.0 release.
git tar-tree v1.4.0^{tree} git-1.4.0 | gzip >git-1.4.0.tar.gz
Create a tarball for v1.4.0 release, but without a global extended pax header.
git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar
Get a tarball v1.4.0 from example.com.
git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar
Put everything in the current head's Documentation/ directory into git-1.4.0-docs.tar, with the prefix git-docs/.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-TAR-TREE(1)