From: Bernt Hansen <bernt@norang.ca>
To: Daniel Mahler <dmahler@gmail.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: *.bak files in trunk?
Date: Tue, 29 Jun 2010 07:40:21 -0400 [thread overview]
Message-ID: <878w5yawyi.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <AANLkTinMYzFy-XOnPpvBCbKZt9MZrXXo8RWrOCjBETnl@mail.gmail.com> (Daniel Mahler's message of "Tue\, 29 Jun 2010 13\:05\:33 +0200")
Daniel Mahler <dmahler@gmail.com> writes:
> On Tue, Jun 29, 2010 at 6:27 AM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>>
>> On Jun 29, 2010, at 2:45 AM, Bernt Hansen wrote:
>>
>>> Daniel Mahler <dmahler@gmail.com> writes:
>>>
>>>> Is this normal?
>>>>
>>>> mahler:~/ELISP/org-mode-git$ git status
>>>> # On branch master
>>>> nothing to commit (working directory clean)
>>>> mahler:~/ELISP/org-mode-git$ find . -name "*.bak"
>>>> ./lisp/ChangeLog.bak
>>>> ./lisp/babel/langs/ob-C.el.bak
>>>
>>> ...
>>>>
>>>> ./lisp/org-capture.el.bak.bak.bak.bak
>>>> ./lisp/org-macs.elc.bak.bak.bak.bak
>>>> ./lisp/org-publish.elc.bak.bak.bak.bak
>>>
>>> You can see untracked files with
>>>
>>> $ git ls-files -o
>>>
>>> $ git ls-files '*.bak'
>>> returns nothing for me so there are no files ending in '.bak' in the
>>> repository as far as I can tell.
>>
>> The bigger problem seems to be that something is creating these files.
>> Bu I have no idea what, noting in Org-mode I would think,
>> must be some utility or stuff in Daniel's setup.
>
> That is the weird thing. The only thing I really
> do in the org directory is "git pull" and make.
> Also not tool I use makes *.bak directories,
> emacs creates *~.
> That, and the fact that git status/diff did not report them,
> made me thing they were from the repository.
> (I do not normally use git)
>
You might want to look at the dates those files were created to see if
you can get any extra information about who creates them. They look to
me like broken editor backup files :) but that's just a guess.
The easiest way to get rid of them is to have git clean them out --
you need to tell it to clean out files and include ignored files which
is what the -x switch does. Make sure you specify the '*.bak' pattern
otherwise it will clean out _everything_ that is not tracked which
includes all of your compiled files.
$ git clean -x '*.bak'
HTH,
Bernt
next prev parent reply other threads:[~2010-06-29 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 18:56 *.bak files in trunk? Daniel Mahler
2010-06-29 0:45 ` Bernt Hansen
2010-06-29 4:27 ` Carsten Dominik
2010-06-29 11:05 ` Daniel Mahler
2010-06-29 11:40 ` Bernt Hansen [this message]
2010-06-29 11:41 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878w5yawyi.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=dmahler@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).