List all recently changed files (recursive)
So, I want to display (via ls
for example) all files, which were changed in the last seven days. If I'm in my docroot-folder, it should be able to look "deeper".
For example:
File Last changed
docroot
|- myfile1 30.11.2015
|- myfile2 10.11.2015
|- MySub
|-sub1 30.11.2015
|-sub2 10.11.2015
So, the ls
(or whatever fits) should output myfile1
and (if possible)
MySub/sub1
.
Is this doable with one command?
command-line search ls
add a comment |
So, I want to display (via ls
for example) all files, which were changed in the last seven days. If I'm in my docroot-folder, it should be able to look "deeper".
For example:
File Last changed
docroot
|- myfile1 30.11.2015
|- myfile2 10.11.2015
|- MySub
|-sub1 30.11.2015
|-sub2 10.11.2015
So, the ls
(or whatever fits) should output myfile1
and (if possible)
MySub/sub1
.
Is this doable with one command?
command-line search ls
add a comment |
So, I want to display (via ls
for example) all files, which were changed in the last seven days. If I'm in my docroot-folder, it should be able to look "deeper".
For example:
File Last changed
docroot
|- myfile1 30.11.2015
|- myfile2 10.11.2015
|- MySub
|-sub1 30.11.2015
|-sub2 10.11.2015
So, the ls
(or whatever fits) should output myfile1
and (if possible)
MySub/sub1
.
Is this doable with one command?
command-line search ls
So, I want to display (via ls
for example) all files, which were changed in the last seven days. If I'm in my docroot-folder, it should be able to look "deeper".
For example:
File Last changed
docroot
|- myfile1 30.11.2015
|- myfile2 10.11.2015
|- MySub
|-sub1 30.11.2015
|-sub2 10.11.2015
So, the ls
(or whatever fits) should output myfile1
and (if possible)
MySub/sub1
.
Is this doable with one command?
command-line search ls
command-line search ls
edited Nov 30 '15 at 9:25
hg8
9,784125391
9,784125391
asked Nov 30 '15 at 9:17
DasSaffeDasSaffe
192117
192117
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
Of course. From the directory you are in do:
find . -type f -mtime -7 -exec ls -l {} ;
Add a redirection to it (aka > results.txt
to store them into that file).
type f
does only files and not directories
mtime -7
does 7 days ago up to now (+7 would be 'older than 7 days')- and it then feeds it to
ls
to show a long list
You can play with the ls -l
part too:
find . -type f -mtime -7 -exec ls -Rl --time-style=long-iso {} ;
find . -type f -mtime -7 -exec ls -R --time-style=long-iso {} ;
will show a tree like method with directories in between the files in long list (1) or short list (2).
4
find
hasls
option so you could just dofind . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
Also it is more appropriate to usefind ... -exec ls -l {} +
which executesls -l
much more efficiently - fewer times with multiple parameters. This is a standard option offind
specified by POSIX.
– pabouk
Nov 30 '15 at 12:30
add a comment |
With zsh
:
ls -l **/*(.m-7)
**/*
will look for files recursively starting from current directory(.m-7)
is glob qualifier where.
indicates regular file,m-7
indicates files that were modified within last 7 days
add a comment |
Not exactly what was asked for... but much easier to remember...
ls -alRt docroot
or
ls -alRt /path/to/top/level/directory
add a comment |
7 days that's 60 seconds*60minutes*24hours*7days
= 604800 seconds
Find out current date in seconds (Unix epoch time):
$ date +%s
1448876323
Subtract the 7 days in seconds:
expr $(date +%s) - 604800
1448271548
Now take stat
command and print stats for all files in format "name + time in seconds" and use awk
to crop off those files whose modification time is greater that that date we calculated
$ stat --printf="%n %Yn" $HOME/* | awk '$2 > 1448271265 {print $0}'
/home/xieerqi/1448428697574.png 1448429613
/home/xieerqi/1448763343273.png 1448763478
/home/xieerqi/1510DRIVE 1448352453
/home/xieerqi/addRemoveDistribution 1448666843
/home/xieerqi/add-update.awk 1448716356
/home/xieerqi/add-update.sh 1448625092
Particularly of interest are last 3 files, because I know I was working them on less that 7 days ago. Thus I know it works
2
Note that instead ofawk '$2 > 1448271265 {print $0}'
you can diretly sayawk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.
– fedorqui
Nov 30 '15 at 16:09
add a comment |
The following command works a dream on Mac OSX - maybe also on ubuntu …
find . -type f -mtime -7 -exec stat -lt "%Y-%m-%d %H:%M:%S" {} ; | cut -d -f6- | sort -r
This finds files in the current directory tree which have been modified in the last 7 days, outputs the modification date + time and path, sorted newest first.
Example output:
2018-02-21 22:06:30 ./fmxmlsnippet.xml
2018-02-19 12:56:01 ./diff.html
2018-02-19 12:44:37 ./temp/iDDR/XMSC_fmxmlsnippet.xml
2018-02-18 22:04:05 ./temp/iDDR/XMFD_fmxmlsnippet.xml
2018-02-15 10:18:27 ./xml/iDDR/XML2_fmxmlsnippet.xml
2018-02-15 10:13:29 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout.xsl
2018-02-15 10:11:36 ./xsl/.DS_Store
2018-02-15 10:10:51 ./xsl/_inc/inc.XML2_fmCM_ReportReferencesToExternalFiles.xsl
2018-02-15 10:10:09 ./xsl/_inc/.DS_Store
2018-02-15 10:07:35 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout-NoAnchors.xsl
2018-02-15 10:07:35 ./xsl/_inc/inc.XML2_fmCM_AnalyseLayout.xsl
I'd be grateful of any feedback from ubuntu users.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f704160%2flist-all-recently-changed-files-recursive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Of course. From the directory you are in do:
find . -type f -mtime -7 -exec ls -l {} ;
Add a redirection to it (aka > results.txt
to store them into that file).
type f
does only files and not directories
mtime -7
does 7 days ago up to now (+7 would be 'older than 7 days')- and it then feeds it to
ls
to show a long list
You can play with the ls -l
part too:
find . -type f -mtime -7 -exec ls -Rl --time-style=long-iso {} ;
find . -type f -mtime -7 -exec ls -R --time-style=long-iso {} ;
will show a tree like method with directories in between the files in long list (1) or short list (2).
4
find
hasls
option so you could just dofind . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
Also it is more appropriate to usefind ... -exec ls -l {} +
which executesls -l
much more efficiently - fewer times with multiple parameters. This is a standard option offind
specified by POSIX.
– pabouk
Nov 30 '15 at 12:30
add a comment |
Of course. From the directory you are in do:
find . -type f -mtime -7 -exec ls -l {} ;
Add a redirection to it (aka > results.txt
to store them into that file).
type f
does only files and not directories
mtime -7
does 7 days ago up to now (+7 would be 'older than 7 days')- and it then feeds it to
ls
to show a long list
You can play with the ls -l
part too:
find . -type f -mtime -7 -exec ls -Rl --time-style=long-iso {} ;
find . -type f -mtime -7 -exec ls -R --time-style=long-iso {} ;
will show a tree like method with directories in between the files in long list (1) or short list (2).
4
find
hasls
option so you could just dofind . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
Also it is more appropriate to usefind ... -exec ls -l {} +
which executesls -l
much more efficiently - fewer times with multiple parameters. This is a standard option offind
specified by POSIX.
– pabouk
Nov 30 '15 at 12:30
add a comment |
Of course. From the directory you are in do:
find . -type f -mtime -7 -exec ls -l {} ;
Add a redirection to it (aka > results.txt
to store them into that file).
type f
does only files and not directories
mtime -7
does 7 days ago up to now (+7 would be 'older than 7 days')- and it then feeds it to
ls
to show a long list
You can play with the ls -l
part too:
find . -type f -mtime -7 -exec ls -Rl --time-style=long-iso {} ;
find . -type f -mtime -7 -exec ls -R --time-style=long-iso {} ;
will show a tree like method with directories in between the files in long list (1) or short list (2).
Of course. From the directory you are in do:
find . -type f -mtime -7 -exec ls -l {} ;
Add a redirection to it (aka > results.txt
to store them into that file).
type f
does only files and not directories
mtime -7
does 7 days ago up to now (+7 would be 'older than 7 days')- and it then feeds it to
ls
to show a long list
You can play with the ls -l
part too:
find . -type f -mtime -7 -exec ls -Rl --time-style=long-iso {} ;
find . -type f -mtime -7 -exec ls -R --time-style=long-iso {} ;
will show a tree like method with directories in between the files in long list (1) or short list (2).
edited Dec 5 '15 at 9:03
Fabby
26.7k1360161
26.7k1360161
answered Nov 30 '15 at 9:22
RinzwindRinzwind
206k28397528
206k28397528
4
find
hasls
option so you could just dofind . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
Also it is more appropriate to usefind ... -exec ls -l {} +
which executesls -l
much more efficiently - fewer times with multiple parameters. This is a standard option offind
specified by POSIX.
– pabouk
Nov 30 '15 at 12:30
add a comment |
4
find
hasls
option so you could just dofind . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
Also it is more appropriate to usefind ... -exec ls -l {} +
which executesls -l
much more efficiently - fewer times with multiple parameters. This is a standard option offind
specified by POSIX.
– pabouk
Nov 30 '15 at 12:30
4
4
find
has ls
option so you could just do find . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
find
has ls
option so you could just do find . -type f -mtime -7 -ls
– heemayl
Nov 30 '15 at 9:33
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
Sure but this makes it a bit more generic (I use this method to find files I need to -remove- and can change that command to do it :) )
– Rinzwind
Nov 30 '15 at 10:03
2
2
Also it is more appropriate to use
find ... -exec ls -l {} +
which executes ls -l
much more efficiently - fewer times with multiple parameters. This is a standard option of find
specified by POSIX.– pabouk
Nov 30 '15 at 12:30
Also it is more appropriate to use
find ... -exec ls -l {} +
which executes ls -l
much more efficiently - fewer times with multiple parameters. This is a standard option of find
specified by POSIX.– pabouk
Nov 30 '15 at 12:30
add a comment |
With zsh
:
ls -l **/*(.m-7)
**/*
will look for files recursively starting from current directory(.m-7)
is glob qualifier where.
indicates regular file,m-7
indicates files that were modified within last 7 days
add a comment |
With zsh
:
ls -l **/*(.m-7)
**/*
will look for files recursively starting from current directory(.m-7)
is glob qualifier where.
indicates regular file,m-7
indicates files that were modified within last 7 days
add a comment |
With zsh
:
ls -l **/*(.m-7)
**/*
will look for files recursively starting from current directory(.m-7)
is glob qualifier where.
indicates regular file,m-7
indicates files that were modified within last 7 days
With zsh
:
ls -l **/*(.m-7)
**/*
will look for files recursively starting from current directory(.m-7)
is glob qualifier where.
indicates regular file,m-7
indicates files that were modified within last 7 days
answered Nov 30 '15 at 9:31
heemaylheemayl
66.8k8141214
66.8k8141214
add a comment |
add a comment |
Not exactly what was asked for... but much easier to remember...
ls -alRt docroot
or
ls -alRt /path/to/top/level/directory
add a comment |
Not exactly what was asked for... but much easier to remember...
ls -alRt docroot
or
ls -alRt /path/to/top/level/directory
add a comment |
Not exactly what was asked for... but much easier to remember...
ls -alRt docroot
or
ls -alRt /path/to/top/level/directory
Not exactly what was asked for... but much easier to remember...
ls -alRt docroot
or
ls -alRt /path/to/top/level/directory
edited Feb 11 '16 at 10:22
David Foerster
28.2k1365111
28.2k1365111
answered Feb 11 '16 at 1:06
heynnemaheynnema
19.1k22156
19.1k22156
add a comment |
add a comment |
7 days that's 60 seconds*60minutes*24hours*7days
= 604800 seconds
Find out current date in seconds (Unix epoch time):
$ date +%s
1448876323
Subtract the 7 days in seconds:
expr $(date +%s) - 604800
1448271548
Now take stat
command and print stats for all files in format "name + time in seconds" and use awk
to crop off those files whose modification time is greater that that date we calculated
$ stat --printf="%n %Yn" $HOME/* | awk '$2 > 1448271265 {print $0}'
/home/xieerqi/1448428697574.png 1448429613
/home/xieerqi/1448763343273.png 1448763478
/home/xieerqi/1510DRIVE 1448352453
/home/xieerqi/addRemoveDistribution 1448666843
/home/xieerqi/add-update.awk 1448716356
/home/xieerqi/add-update.sh 1448625092
Particularly of interest are last 3 files, because I know I was working them on less that 7 days ago. Thus I know it works
2
Note that instead ofawk '$2 > 1448271265 {print $0}'
you can diretly sayawk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.
– fedorqui
Nov 30 '15 at 16:09
add a comment |
7 days that's 60 seconds*60minutes*24hours*7days
= 604800 seconds
Find out current date in seconds (Unix epoch time):
$ date +%s
1448876323
Subtract the 7 days in seconds:
expr $(date +%s) - 604800
1448271548
Now take stat
command and print stats for all files in format "name + time in seconds" and use awk
to crop off those files whose modification time is greater that that date we calculated
$ stat --printf="%n %Yn" $HOME/* | awk '$2 > 1448271265 {print $0}'
/home/xieerqi/1448428697574.png 1448429613
/home/xieerqi/1448763343273.png 1448763478
/home/xieerqi/1510DRIVE 1448352453
/home/xieerqi/addRemoveDistribution 1448666843
/home/xieerqi/add-update.awk 1448716356
/home/xieerqi/add-update.sh 1448625092
Particularly of interest are last 3 files, because I know I was working them on less that 7 days ago. Thus I know it works
2
Note that instead ofawk '$2 > 1448271265 {print $0}'
you can diretly sayawk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.
– fedorqui
Nov 30 '15 at 16:09
add a comment |
7 days that's 60 seconds*60minutes*24hours*7days
= 604800 seconds
Find out current date in seconds (Unix epoch time):
$ date +%s
1448876323
Subtract the 7 days in seconds:
expr $(date +%s) - 604800
1448271548
Now take stat
command and print stats for all files in format "name + time in seconds" and use awk
to crop off those files whose modification time is greater that that date we calculated
$ stat --printf="%n %Yn" $HOME/* | awk '$2 > 1448271265 {print $0}'
/home/xieerqi/1448428697574.png 1448429613
/home/xieerqi/1448763343273.png 1448763478
/home/xieerqi/1510DRIVE 1448352453
/home/xieerqi/addRemoveDistribution 1448666843
/home/xieerqi/add-update.awk 1448716356
/home/xieerqi/add-update.sh 1448625092
Particularly of interest are last 3 files, because I know I was working them on less that 7 days ago. Thus I know it works
7 days that's 60 seconds*60minutes*24hours*7days
= 604800 seconds
Find out current date in seconds (Unix epoch time):
$ date +%s
1448876323
Subtract the 7 days in seconds:
expr $(date +%s) - 604800
1448271548
Now take stat
command and print stats for all files in format "name + time in seconds" and use awk
to crop off those files whose modification time is greater that that date we calculated
$ stat --printf="%n %Yn" $HOME/* | awk '$2 > 1448271265 {print $0}'
/home/xieerqi/1448428697574.png 1448429613
/home/xieerqi/1448763343273.png 1448763478
/home/xieerqi/1510DRIVE 1448352453
/home/xieerqi/addRemoveDistribution 1448666843
/home/xieerqi/add-update.awk 1448716356
/home/xieerqi/add-update.sh 1448625092
Particularly of interest are last 3 files, because I know I was working them on less that 7 days ago. Thus I know it works
answered Nov 30 '15 at 9:41
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72k9148314
72k9148314
2
Note that instead ofawk '$2 > 1448271265 {print $0}'
you can diretly sayawk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.
– fedorqui
Nov 30 '15 at 16:09
add a comment |
2
Note that instead ofawk '$2 > 1448271265 {print $0}'
you can diretly sayawk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.
– fedorqui
Nov 30 '15 at 16:09
2
2
Note that instead of
awk '$2 > 1448271265 {print $0}'
you can diretly say awk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.– fedorqui
Nov 30 '15 at 16:09
Note that instead of
awk '$2 > 1448271265 {print $0}'
you can diretly say awk '$2 > 1448271265'
. On a true condition, awk prints the current line as a default action.– fedorqui
Nov 30 '15 at 16:09
add a comment |
The following command works a dream on Mac OSX - maybe also on ubuntu …
find . -type f -mtime -7 -exec stat -lt "%Y-%m-%d %H:%M:%S" {} ; | cut -d -f6- | sort -r
This finds files in the current directory tree which have been modified in the last 7 days, outputs the modification date + time and path, sorted newest first.
Example output:
2018-02-21 22:06:30 ./fmxmlsnippet.xml
2018-02-19 12:56:01 ./diff.html
2018-02-19 12:44:37 ./temp/iDDR/XMSC_fmxmlsnippet.xml
2018-02-18 22:04:05 ./temp/iDDR/XMFD_fmxmlsnippet.xml
2018-02-15 10:18:27 ./xml/iDDR/XML2_fmxmlsnippet.xml
2018-02-15 10:13:29 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout.xsl
2018-02-15 10:11:36 ./xsl/.DS_Store
2018-02-15 10:10:51 ./xsl/_inc/inc.XML2_fmCM_ReportReferencesToExternalFiles.xsl
2018-02-15 10:10:09 ./xsl/_inc/.DS_Store
2018-02-15 10:07:35 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout-NoAnchors.xsl
2018-02-15 10:07:35 ./xsl/_inc/inc.XML2_fmCM_AnalyseLayout.xsl
I'd be grateful of any feedback from ubuntu users.
add a comment |
The following command works a dream on Mac OSX - maybe also on ubuntu …
find . -type f -mtime -7 -exec stat -lt "%Y-%m-%d %H:%M:%S" {} ; | cut -d -f6- | sort -r
This finds files in the current directory tree which have been modified in the last 7 days, outputs the modification date + time and path, sorted newest first.
Example output:
2018-02-21 22:06:30 ./fmxmlsnippet.xml
2018-02-19 12:56:01 ./diff.html
2018-02-19 12:44:37 ./temp/iDDR/XMSC_fmxmlsnippet.xml
2018-02-18 22:04:05 ./temp/iDDR/XMFD_fmxmlsnippet.xml
2018-02-15 10:18:27 ./xml/iDDR/XML2_fmxmlsnippet.xml
2018-02-15 10:13:29 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout.xsl
2018-02-15 10:11:36 ./xsl/.DS_Store
2018-02-15 10:10:51 ./xsl/_inc/inc.XML2_fmCM_ReportReferencesToExternalFiles.xsl
2018-02-15 10:10:09 ./xsl/_inc/.DS_Store
2018-02-15 10:07:35 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout-NoAnchors.xsl
2018-02-15 10:07:35 ./xsl/_inc/inc.XML2_fmCM_AnalyseLayout.xsl
I'd be grateful of any feedback from ubuntu users.
add a comment |
The following command works a dream on Mac OSX - maybe also on ubuntu …
find . -type f -mtime -7 -exec stat -lt "%Y-%m-%d %H:%M:%S" {} ; | cut -d -f6- | sort -r
This finds files in the current directory tree which have been modified in the last 7 days, outputs the modification date + time and path, sorted newest first.
Example output:
2018-02-21 22:06:30 ./fmxmlsnippet.xml
2018-02-19 12:56:01 ./diff.html
2018-02-19 12:44:37 ./temp/iDDR/XMSC_fmxmlsnippet.xml
2018-02-18 22:04:05 ./temp/iDDR/XMFD_fmxmlsnippet.xml
2018-02-15 10:18:27 ./xml/iDDR/XML2_fmxmlsnippet.xml
2018-02-15 10:13:29 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout.xsl
2018-02-15 10:11:36 ./xsl/.DS_Store
2018-02-15 10:10:51 ./xsl/_inc/inc.XML2_fmCM_ReportReferencesToExternalFiles.xsl
2018-02-15 10:10:09 ./xsl/_inc/.DS_Store
2018-02-15 10:07:35 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout-NoAnchors.xsl
2018-02-15 10:07:35 ./xsl/_inc/inc.XML2_fmCM_AnalyseLayout.xsl
I'd be grateful of any feedback from ubuntu users.
The following command works a dream on Mac OSX - maybe also on ubuntu …
find . -type f -mtime -7 -exec stat -lt "%Y-%m-%d %H:%M:%S" {} ; | cut -d -f6- | sort -r
This finds files in the current directory tree which have been modified in the last 7 days, outputs the modification date + time and path, sorted newest first.
Example output:
2018-02-21 22:06:30 ./fmxmlsnippet.xml
2018-02-19 12:56:01 ./diff.html
2018-02-19 12:44:37 ./temp/iDDR/XMSC_fmxmlsnippet.xml
2018-02-18 22:04:05 ./temp/iDDR/XMFD_fmxmlsnippet.xml
2018-02-15 10:18:27 ./xml/iDDR/XML2_fmxmlsnippet.xml
2018-02-15 10:13:29 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout.xsl
2018-02-15 10:11:36 ./xsl/.DS_Store
2018-02-15 10:10:51 ./xsl/_inc/inc.XML2_fmCM_ReportReferencesToExternalFiles.xsl
2018-02-15 10:10:09 ./xsl/_inc/.DS_Store
2018-02-15 10:07:35 ./xsl/fmxmlsnippet/XML2_fmCM_AnalyseLayout-NoAnchors.xsl
2018-02-15 10:07:35 ./xsl/_inc/inc.XML2_fmCM_AnalyseLayout.xsl
I'd be grateful of any feedback from ubuntu users.
answered Feb 21 '18 at 21:53
MrWatsonMrWatson
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f704160%2flist-all-recently-changed-files-recursive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown