emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Daniel Mahler <dmahler@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Re: *.bak files in trunk?
Date: Tue, 29 Jun 2010 06:27:43 +0200	[thread overview]
Message-ID: <3579339C-B0FA-4686-8D28-DC2B4D74CE3E@gmail.com> (raw)
In-Reply-To: <87pqzabr9v.fsf@gollum.intra.norang.ca>


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
>
> Hi Daniel,
>
> I don't think those files are in the repository but they are in  your
> local working directory.  There is an entry '*.bak' in the .gitignore
> file in the repository so 'git status' will not show these files by
> default (since they are ignored).
>
> 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.

- Carsten

  reply	other threads:[~2010-06-29  4:27 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 [this message]
2010-06-29 11:05     ` Daniel Mahler
2010-06-29 11:40       ` Bernt Hansen
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=3579339C-B0FA-4686-8D28-DC2B4D74CE3E@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bernt@norang.ca \
    --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).