{"thread":{"id":"14264","subject":"finding deleted file names","startedAt":"2008-07-03T00:01:55Z","lastAt":"2008-07-07T00:41:05Z","messageCount":16,"participants":["Geoff Russell","Mikael Magnusson","Johannes Schindelin","Jakub Narebski","Jeff King","Junio C Hamano","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"82044","messageId":"93c3eada0807021701m13b7adddv51537f4cf9d52533@mail.gmail.com","threadId":"14264","inReplyTo":null,"subject":"finding deleted file names","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2008-07-03T00:01:55Z","receivedAt":"2008-07-03T00:01:55Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n\nfinds files deleted during the last 7 days, but if my repository is\nonly 6 days old I get a\nfatal error.\n\nfatal: bad object HEAD@{7 days ago}\n\nIs there something that says \"since repository creation\", ie., go back as far\nas possible, but no further? Is there a symbolic name for the initial commit?\n\nCheers,\nGeoff Russell\n"},{"id":"82055","messageId":"237967ef0807021812r3ccbfbacg2cb6b12358d2ee2e@mail.gmail.com","threadId":"14264","inReplyTo":"93c3eada0807021701m13b7adddv51537f4cf9d52533@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Mikael Magnusson","fromEmail":"mikachu@gmail.com","sentAt":"2008-07-03T01:12:44Z","receivedAt":"2008-07-03T01:12:44Z","isPatch":false,"sender":{"key":"mikachu@gmail.com","avatar":null},"body":"2008/7/3 Geoff Russell :\n> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n>\n> finds files deleted during the last 7 days, but if my repository is\n> only 6 days old I get a\n> fatal error.\n>\n> fatal: bad object HEAD@{7 days ago}\n>\n> Is there something that says \"since repository creation\", ie., go back as far\n> as possible, but no further? Is there a symbolic name for the initial commit?\n\nThere's no symbolic name for it, since there might not be only one initial\ncommit. git.git for example has at least three root commits. You will\nprobably get what you want with $(git rev-list HEAD|tail -1). If your\nhistory is very large, $(git rev-list --reverse HEAD|head -1) is slightly\nfaster, but usually not enough to offset typing --reverse :).\n\n-- \nMikael Magnusson\n"},{"id":"82084","messageId":"93c3eada0807021945la3e565csc50eed4b14feb9c3@mail.gmail.com","threadId":"14264","inReplyTo":"237967ef0807021812r3ccbfbacg2cb6b12358d2ee2e@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2008-07-03T02:45:37Z","receivedAt":"2008-07-03T02:45:37Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"On Thu, Jul 3, 2008 at 10:42 AM, Mikael Magnusson wrote:\n> 2008/7/3 Geoff Russell :\n>> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n>>\n>> finds files deleted during the last 7 days, but if my repository is\n>> only 6 days old I get a\n>> fatal error.\n>>\n>> fatal: bad object HEAD@{7 days ago}\n>>\n>> Is there something that says \"since repository creation\", ie., go back as far\n>> as possible, but no further? Is there a symbolic name for the initial commit?\n>\n> There's no symbolic name for it, since there might not be only one initial\n> commit. git.git for example has at least three root commits. You will\n> probably get what you want with $(git rev-list HEAD|tail -1). If your\n> history is very large, $(git rev-list --reverse HEAD|head -1) is slightly\n> faster, but usually not enough to offset typing --reverse :).\n\nThanks for this, but I'm a little confused.\n\nIf I do a \"git init\", there must be a first commit after this? Isn't\nthis the first commit, how\ncan there be more than one first commit?\n\nCheers,\nGeoff\n\n>\n> --\n> Mikael Magnusson\n>\n\n\n\n-- \n6 Fifth Ave,\nSt Morris, S.A. 5068\nAustralia\nPh: 041 8805 184 / 08 8332 5069\n"},{"id":"82086","messageId":"237967ef0807022018t31912870gf0490acf5ccef5eb@mail.gmail.com","threadId":"14264","inReplyTo":"93c3eada0807021945la3e565csc50eed4b14feb9c3@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Mikael Magnusson","fromEmail":"mikachu@gmail.com","sentAt":"2008-07-03T03:18:18Z","receivedAt":"2008-07-03T03:18:18Z","isPatch":false,"sender":{"key":"mikachu@gmail.com","avatar":null},"body":"2008/7/3 Geoff Russell :\n> On Thu, Jul 3, 2008 at 10:42 AM, Mikael Magnusson wrote:\n>> 2008/7/3 Geoff Russell :\n>>> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n>>>\n>>> finds files deleted during the last 7 days, but if my repository is\n>>> only 6 days old I get a\n>>> fatal error.\n>>>\n>>> fatal: bad object HEAD@{7 days ago}\n>>>\n>>> Is there something that says \"since repository creation\", ie., go back as far\n>>> as possible, but no further? Is there a symbolic name for the initial commit?\n>>\n>> There's no symbolic name for it, since there might not be only one initial\n>> commit. git.git for example has at least three root commits. You will\n>> probably get what you want with $(git rev-list HEAD|tail -1). If your\n>> history is very large, $(git rev-list --reverse HEAD|head -1) is slightly\n>> faster, but usually not enough to offset typing --reverse :).\n>\n> Thanks for this, but I'm a little confused.\n>\n> If I do a \"git init\", there must be a first commit after this? Isn't\n> this the first commit, how\n> can there be more than one first commit?\n\nIn git.git, the gitk subdirectory has a separate root because it was merged\nwith the subtree merge strategy, so if you go down the second parent of that\nmerge commit, you'll end up not at the start of the git history. You can\nsee this if you just fetch any other repo into your current one and merge it.\nJust add everything with conflict markers in if it conflicts and commit,\nthen look at gitk :). (and obviously then revert the merge or whatever).\n\nBtw, after you git init, there are 0 commits, the first commit is created\nwhen you run git commit the first time.\n\n-- \nMikael Magnusson\n"},{"id":"82111","messageId":"m3hcb7fho7.fsf@localhost.localdomain","threadId":"14264","inReplyTo":"93c3eada0807021701m13b7adddv51537f4cf9d52533@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-07-03T09:20:14Z","receivedAt":"2008-07-03T09:20:14Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"\"Geoff Russell\" writes:\n\n> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n\nWhat did you want to find here?\n\n> finds files deleted during the last 7 days, but if my repository is\n> only 6 days old I get a fatal error.\n> \n> fatal: bad object HEAD@{7 days ago}\n\nFirst, which version of git do you use? Because with git version 1.5.6.1\nI get:\n\n 1000:[master!git]$ git diff --diff-filter=D --name-only HEAD@{'10 years ago'}\n warning: Log for 'HEAD' only goes back to Fri, 4 Apr 2008 15:28:53 +0200.\n Documentation/core-tutorial.txt\n [...]\n\nSecond, []@{} refers to _local_ history of where _branch tip_\npointed in your repository, and is purely local information retrieved from\nreflogs (which gets pruned / expired). To refer to (find) commits by\ncommit creation date, use --since=/--after= or --until=/\n/--before=. There was even lately added information to git\ndocumentation about difference bwetween []@{} and --before=\nand when to use one or the other.\n\n> Is there something that says \"since repository creation\", ie., go back as far\n> as possible, but no further? Is there a symbolic name for the initial commit?\n\nBecause git allows joining two repositories into one (either union of\ntheir top directories, or one put into subdirectory in other using so\ncalled 'subtree' merge strategy) there can be more than one \"root\"\n(parentless) commit. In git repository there are 7 root commits, not\ncounting \"disjoint\" branches like 'html', 'man' and 'todo' which share\nno history and doesn't join with mainline history.\n\nThey are: git-p4 (Perforce importer), git-gui, gitweb, gitk, git mail\ntools, git,... and something strange (4e00220243).\n\n $ git rev-list --parents --branches --not html man todo | grep -v -e ' '\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"82114","messageId":"20080703103658.GA11571@sigill.intra.peff.net","threadId":"14264","inReplyTo":"93c3eada0807021701m13b7adddv51537f4cf9d52533@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2008-07-03T10:36:59Z","receivedAt":"2008-07-03T10:36:59Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jul 03, 2008 at 09:31:55AM +0930, Geoff Russell wrote:\n\n> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n> \n> finds files deleted during the last 7 days, but if my repository is\n> only 6 days old I get a\n> fatal error.\n> \n> fatal: bad object HEAD@{7 days ago}\n\nThis should issue a warning, but use the oldest reflog entry. However,\nthere is a slight problem with that. See below for details.\n\nShawn, does this seem sane to you?\n\n-- >8 --\navoid null SHA1 in oldest reflog\n\nWhen the user specifies a ref by a reflog entry older than\none we have (e.g., \"HEAD@{20 years ago\"}), we issue a\nwarning and give them the \"from\" value of the oldest reflog\nentry. That is, we say \"we don't know what happened before\nthis entry, but before this we know we had some particular\nSHA1\".\n\nHowever, the oldest reflog entry is often a creation event\nsuch as clone or branch creation. In this case, the entry\nclaims that the ref went from \"00000...\" (the null sha1) to\nthe new value, and the reflog lookup returns the null sha1.\n\nWhile this is technically correct (the entry tells us that\nthe ref didn't exist at the specified time) it is not\nterribly useful to the end user. What they probably want\ninstead is \"the oldest useful sha1 that this ref ever had\".\nThis patch changes the behavior such that if the oldest\nreflog entry would return the null sha1, it instead returns\nthe first actual value the ref ever had.\n\nWe never discovered this problem in the test scripts because\nwe created \"fake\" reflogs that had only a specified segment\nof history. This patch updates the tests with a creation\nevent at the beginning of history.\n\nSigned-off-by: Jeff King \n---\n refs.c | 4 ++++\n t/t1400-update-ref.sh | 9 ++++++++-\n 2 files changed, 12 insertions(+), 1 deletions(-)\n\ndiff --git a/refs.c b/refs.c\nindex 9e8e858..6c6e9e5 100644\n--- a/refs.c\n+++ b/refs.c\n@@ -1412,6 +1412,10 @@ int read_ref_at(const char *ref, unsigned long at_time, int cnt, unsigned char *\n \ttz = strtoul(tz_c, NULL, 10);\n \tif (get_sha1_hex(logdata, sha1))\n \t\tdie(\"Log %s is corrupt.\", logfile);\n+\tif (is_null_sha1(sha1)) {\n+\t\tif (get_sha1_hex(logdata + 41, sha1))\n+\t\t\tdie(\"Log %s is corrupt.\", logfile);\n+\t}\n \tif (msg)\n \t\t*msg = ref_msg(logdata, logend);\n \tmunmap(log_mapped, mapsz);\ndiff --git a/t/t1400-update-ref.sh b/t/t1400-update-ref.sh\nindex f387d46..ca99d37 100755\n--- a/t/t1400-update-ref.sh\n+++ b/t/t1400-update-ref.sh\n@@ -155,7 +155,8 @@ rm -f .git/$m .git/logs/$m expect\n \n git update-ref $m $D\n cat >.git/logs/$m < 1117150320 -0500\n+0000000000000000000000000000000000000000 $C $GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> 1117150320 -0500\n+$C $A $GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> 1117150350 -0500\n $A $B $GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> 1117150380 -0500\n $F $Z $GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> 1117150680 -0500\n $Z $E $GIT_COMMITTER_NAME <$GIT_COMMITTER_EMAIL> 1117150980 -0500\n@@ -186,6 +187,12 @@ test_expect_success \\\n \t'Query \"master@{May 26 2005 23:32:00}\" (exactly history start)' \\\n \t'rm -f o e\n \t git rev-parse --verify \"master@{May 26 2005 23:32:00}\" >o 2>e &&\n+\t test '\"$C\"' = $(cat o) &&\n+\t test \"\" = \"$(cat e)\"'\n+test_expect_success \\\n+\t'Query \"master@{May 26 2005 23:32:30}\" (first non-creation change)' \\\n+\t'rm -f o e\n+\t git rev-parse --verify \"master@{May 26 2005 23:32:30}\" >o 2>e &&\n \t test '\"$A\"' = $(cat o) &&\n \t test \"\" = \"$(cat e)\"'\n test_expect_success \\\n-- \n1.5.6.1.282.g8aee2.dirty\n"},{"id":"82116","messageId":"20080703104233.GA26162@sigill.intra.peff.net","threadId":"14264","inReplyTo":"93c3eada0807021945la3e565csc50eed4b14feb9c3@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2008-07-03T10:42:33Z","receivedAt":"2008-07-03T10:42:33Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jul 03, 2008 at 12:15:37PM +0930, Geoff Russell wrote:\n\n> >> Is there something that says \"since repository creation\", ie., go back as far\n> >> as possible, but no further? Is there a symbolic name for the initial commit?\n> >\n> > There's no symbolic name for it, since there might not be only one initial\n> > commit. git.git for example has at least three root commits. You will\n> > probably get what you want with $(git rev-list HEAD|tail -1). If your\n> > history is very large, $(git rev-list --reverse HEAD|head -1) is slightly\n> > faster, but usually not enough to offset typing --reverse :).\n> \n> Thanks for this, but I'm a little confused.\n> \n> If I do a \"git init\", there must be a first commit after this? Isn't\n> this the first commit, how\n> can there be more than one first commit?\n\nThe confusing part is that you two are talking about two slightly\ndifferent things. If you define \"initial commit\" as \"the commit which\nhas no parents\" then there can be many (you get a new one anytime you\nmerge in a project with unrelated history).\n\nHowever, what Geoff originally mentioned was HEAD{'7 days ago'}, which\nactually looks in the reflog. So if you define \"initial commit\" as \"the\nfirst commit value that this ref ever had\" then there is only one\n(though of course, your reflog will eventually expire, so it won't be\n\"the oldest value this ref ever had\" but rather \"the oldest one the\nreflog ever remembers it having\").\n\n-Peff\n"},{"id":"82104","messageId":"alpine.DEB.1.00.0807031255230.9925@racer","threadId":"14264","inReplyTo":"93c3eada0807021701m13b7adddv51537f4cf9d52533@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-07-03T11:57:22Z","receivedAt":"2008-07-03T11:57:22Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 3 Jul 2008, Geoff Russell wrote:\n\n> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n> \n> finds files deleted during the last 7 days, but if my repository is\n> only 6 days old I get a\n> fatal error.\n> \n> fatal: bad object HEAD@{7 days ago}\n\nSorry, but you haven't grasped the concept of reflogs. The \"@{...}\" is \npurely for the _local_ state.\n\nSo clearly, if you did not have the repo 7 days ago, \"HEAD@{7.days.ago}\" \ndoes not exist.\n\nIn a distributed SCM, asking about a branch's state \"7 days ago\" is \nill-defined at best.\n\nHth,\nDscho\n"},{"id":"82147","messageId":"7vzloyzrew.fsf@gitster.siamese.dyndns.org","threadId":"14264","inReplyTo":"20080703103658.GA11571@sigill.intra.peff.net","subject":"Re: finding deleted file names","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-07-03T19:41:43Z","receivedAt":"2008-07-03T19:41:43Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> On Thu, Jul 03, 2008 at 09:31:55AM +0930, Geoff Russell wrote:\n>\n>> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n>> \n>> finds files deleted during the last 7 days, but if my repository is\n>> only 6 days old I get a\n>> fatal error.\n>> \n>> fatal: bad object HEAD@{7 days ago}\n>\n> This should issue a warning, but use the oldest reflog entry. However,\n> there is a slight problem with that. See below for details.\n\nI think your patch is a sane thing to do.\n\nOnce reflog entries begin expiring, we won't have the null_sha1 on the\nprevious side of them, and after that we will keep returning the\noldest-known one, so nobody should be expecting to find out when a ref was\nfirst created in this repository by checking with what timestamp that\nsyntax breaks in the existing interface.\n\nSorry for not being Shawn ;-)\n"},{"id":"82148","messageId":"20080703194728.GA18443@sigill.intra.peff.net","threadId":"14264","inReplyTo":"7vzloyzrew.fsf@gitster.siamese.dyndns.org","subject":"Re: finding deleted file names","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2008-07-03T19:47:28Z","receivedAt":"2008-07-03T19:47:28Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jul 03, 2008 at 12:41:43PM -0700, Junio C Hamano wrote:\n\n> Once reflog entries begin expiring, we won't have the null_sha1 on the\n> previous side of them, and after that we will keep returning the\n> oldest-known one, so nobody should be expecting to find out when a ref was\n> first created in this repository by checking with what timestamp that\n> syntax breaks in the existing interface.\n\nRight, that was my thought: though perhaps not technically as precise,\nit is much more DWIM.\n\nMy other concern, which I failed to voice in the original mail was:\nshould we do this magic for other reflog entries besides the first one?\nIt is possible to end up with a null sha1 in any other entry? Branch\ncreation shouldn't do it, because we will have deleted any previous\nreflog when killing off the branch before, so we always end up putting\nin the \"oldest\" reflog entry. Cloning shouldn't do it for obvious\nreasons.\n\n> Sorry for not being Shawn ;-)\n\nHeh.\n\n-Peff\n"},{"id":"82155","messageId":"20080703203224.GA7663@spearce.org","threadId":"14264","inReplyTo":"20080703103658.GA11571@sigill.intra.peff.net","subject":"Re: finding deleted file names","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-07-03T20:32:24Z","receivedAt":"2008-07-03T20:32:24Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jeff King wrote:\n> On Thu, Jul 03, 2008 at 09:31:55AM +0930, Geoff Russell wrote:\n> \n> > git diff --diff-filter=D --name-only HEAD@{'7 days ago'}\n> > \n> > finds files deleted during the last 7 days, but if my repository is\n> > only 6 days old I get a\n> > fatal error.\n> > \n> > fatal: bad object HEAD@{7 days ago}\n> \n> This should issue a warning, but use the oldest reflog entry. However,\n> there is a slight problem with that. See below for details.\n> \n> Shawn, does this seem sane to you?\n\nYea, this is the only reasonable thing to do here. Ack.\n\n-- \nShawn.\n"},{"id":"82207","messageId":"93c3eada0807032345r2ff59d69kca42bc9ea7782f31@mail.gmail.com","threadId":"14264","inReplyTo":"20080703104233.GA26162@sigill.intra.peff.net","subject":"Re: finding deleted file names","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2008-07-04T06:45:01Z","receivedAt":"2008-07-04T06:45:01Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"On 7/3/08, Jeff King wrote:\n> On Thu, Jul 03, 2008 at 12:15:37PM +0930, Geoff Russell wrote:\n>\n> > >> Is there something that says \"since repository creation\", ie., go back as far\n> > >> as possible, but no further? Is there a symbolic name for the initial commit?\n> > >\n> > > There's no symbolic name for it, since there might not be only one initial\n> > > commit. git.git for example has at least three root commits. You will\n> > > probably get what you want with $(git rev-list HEAD|tail -1). If your\n> > > history is very large, $(git rev-list --reverse HEAD|head -1) is slightly\n> > > faster, but usually not enough to offset typing --reverse :).\n> >\n> > Thanks for this, but I'm a little confused.\n> >\n> > If I do a \"git init\", there must be a first commit after this? Isn't\n> > this the first commit, how\n> > can there be more than one first commit?\n>\n>\n> The confusing part is that you two are talking about two slightly\n> different things. If you define \"initial commit\" as \"the commit which\n> has no parents\" then there can be many (you get a new one anytime you\n> merge in a project with unrelated history).\n>\n> However, what Geoff originally mentioned was HEAD{'7 days ago'}, which\n> actually looks in the reflog. So if you define \"initial commit\" as \"the\n> first commit value that this ref ever had\" then there is only one\n> (though of course, your reflog will eventually expire, so it won't be\n> \"the oldest value this ref ever had\" but rather \"the oldest one the\n> reflog ever remembers it having\").\n\nYou guys are (quite properly) worried about all the edge cases and I\nhave probably\nconfused things by using the reflog when they may be a better way of\ndoing things.\n\nPerhaps if I describe the problem, there may be a better solution than using the\nreflog. I've made a bunch of changes to a repository, a few weeks\nlater I figure I've\ndeleted a file I need but am not really sure of its name. So I want to list the\nfiles that I've deleted during the past few weeks. So the aim is to\nfind the files that\naren't in the current working directory but that are in some commit done since\nday X.\n\nCheers,\nGeoff\n\n\n>\n> -Peff\n>\n\n\n-- \n6 Fifth Ave,\nSt Morris, S.A. 5068\nAustralia\nPh: 041 8805 184 / 08 8332 5069\n"},{"id":"82208","messageId":"7v1w2aw2lt.fsf@gitster.siamese.dyndns.org","threadId":"14264","inReplyTo":"93c3eada0807032345r2ff59d69kca42bc9ea7782f31@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-07-04T07:05:50Z","receivedAt":"2008-07-04T07:05:50Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Geoff Russell\" writes:\n\n> ... I've made a bunch of changes to a repository, a few weeks later I\n> figure I've deleted a file I need but am not really sure of its name. So\n> I want to list the files that I've deleted during the past few weeks.\n\n$ git log --pretty=oneline --diff-filter=D --name-only -M --since=90.days\n"},{"id":"82334","messageId":"93c3eada0807052154j9de9074s8c5625fb7507b96e@mail.gmail.com","threadId":"14264","inReplyTo":"7v1w2aw2lt.fsf@gitster.siamese.dyndns.org","subject":"Re: finding deleted file names","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2008-07-06T04:54:48Z","receivedAt":"2008-07-06T04:54:48Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"On 7/4/08, Junio C Hamano wrote:\n> \"Geoff Russell\" writes:\n>\n> > ... I've made a bunch of changes to a repository, a few weeks later I\n>\n> > figure I've deleted a file I need but am not really sure of its name. So\n> > I want to list the files that I've deleted during the past few weeks.\n>\n>\n> $ git log --pretty=oneline --diff-filter=D --name-only -M --since=90.days\n\nThis is good, but on my version 1.5.5.1, is giving the commit-ids +\ncomments as well\nas the names.\n\ne.g.,\n 58d331dc02da635a60be5911dd98510f350718ad deleted: 999\nmodified: frepas.tex\n LEAFLETS/999\n 1b7e44fb572297bd5a6f240864dcec292fa158b0 after caption added\n LEAFLETS/xxx.tex\n\nCheers,\nGeoff\n\n\n\n>\n>\n\n\n-- \n6 Fifth Ave,\nSt Morris, S.A. 5068\nAustralia\nPh: 041 8805 184 / 08 8332 5069\n"},{"id":"82336","messageId":"7v63rjpp4s.fsf@gitster.siamese.dyndns.org","threadId":"14264","inReplyTo":"93c3eada0807052154j9de9074s8c5625fb7507b96e@mail.gmail.com","subject":"Re: finding deleted file names","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-07-06T05:17:55Z","receivedAt":"2008-07-06T05:17:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Geoff Russell\" writes:\n\n> On 7/4/08, Junio C Hamano wrote:\n>> \"Geoff Russell\" writes:\n>>\n>> > ... I've made a bunch of changes to a repository, a few weeks later I\n>>\n>> > figure I've deleted a file I need but am not really sure of its name. So\n>> > I want to list the files that I've deleted during the past few weeks.\n>>\n>>\n>> $ git log --pretty=oneline --diff-filter=D --name-only -M --since=90.days\n>\n> This is good, but on my version 1.5.5.1, is giving the commit-ids +\n> comments as well\n> as the names.\n\nOh, I very much intended to give them, as --since=90.days is very broad\nthat you would want to know which exact commit to learn when the found\nchange was made anyway.\n"},{"id":"82407","messageId":"93c3eada0807061741s33e6da08lc1a8b04700d3a0dc@mail.gmail.com","threadId":"14264","inReplyTo":"7v63rjpp4s.fsf@gitster.siamese.dyndns.org","subject":"Re: finding deleted file names","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2008-07-07T00:41:05Z","receivedAt":"2008-07-07T00:41:05Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"On Sun, Jul 6, 2008 at 2:47 PM, Junio C Hamano wrote:\n> \"Geoff Russell\" writes:\n>\n>> On 7/4/08, Junio C Hamano wrote:\n>>> \"Geoff Russell\" writes:\n>>>\n>>> > ... I've made a bunch of changes to a repository, a few weeks later I\n>>>\n>>> > figure I've deleted a file I need but am not really sure of its name. So\n>>> > I want to list the files that I've deleted during the past few weeks.\n>>>\n>>>\n>>> $ git log --pretty=oneline --diff-filter=D --name-only -M --since=90.days\n>>\n>> This is good, but on my version 1.5.5.1, is giving the commit-ids +\n>> comments as well\n>> as the names.\n>\n> Oh, I very much intended to give them, as --since=90.days is very broad\n> that you would want to know which exact commit to learn when the found\n> change was made anyway.\n>\n\nThat's fine, the --name-only confused me, but I understand what is\nhappening now.\n\nGeoff.\n\n\n-- \n6 Fifth Ave,\nSt Morris, S.A. 5068\nAustralia\nPh: 041 8805 184 / 08 8332 5069\n"}]}