lar...@gullik.org (Lars Gullik Bjønnes) writes:
| Alessandro Di Federico <a...@clearmind.me> writes:
>
| | On Fri, 2012-10-26 at 18:03 +0200, Pavel Sanda wrote:
>>> No, it is not. Adding some basic support (#0) like we have with other
>>> RCS
>>> is one weekend work and you'll spend more time on testing than coding.
>>>
>>> Some folks spoke about more fancy git support - in particular
>>> #1) use git for bundled format
>>> #2) use (some of) git codebase instead of relying on external calls
>>> we use for rcs/cvs/svn.
>>
| | Yes, I've read the discussion about git. The problem on when to git-push
| | emerged, but honestly I think that adding a dedicated
| | command/button/menu item is much easier than all the other options like
| | commit+push or just commit. However I may miss something.
>>
| | About #2, if I'm correct the question was just about knowing if the file
| | is part of a git repo since we don't want to spawn a process each time a
| | document is open. In the case we'd have to check "./.git", and
| | "../.git", and "../../.git". I know this may be a problem in certain
| | situations, but that's what git-status does, so we don't have much
| | alternative.
>
| I really think that calling "git status" or a similar command is
| perfectly ok, and while we wait for libgit to emerge, also the right
| thing to do.
git config --local core.repositoryFormatVersion
might be the correct thing to use.
--
Lgb
