zsh-workers
 help / color / mirror / code / Atom feed
From: "Thomas Gstädtner" <thomas@gstaedtner.net>
To: Nikolai Weibull <now@bitwi.se>
Cc: zsh-workers@zsh.org
Subject: Re: Git completion slowness
Date: Fri, 10 Dec 2010 12:54:54 +0100	[thread overview]
Message-ID: <AANLkTimFeBgGqLRSyYMtdRR5scXByDm8EP2RHfgfjtgx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=RiNxd=f4yezvHFd6sVGs-9PvSsM=S=c0p1Ybj@mail.gmail.com>

On Fri, Dec 10, 2010 at 12:37, Nikolai Weibull <now@bitwi.se> wrote:
> On Fri, Dec 10, 2010 at 12:07, Frank Terbeck <ft@bewatermyfriend.org> wrote:
>
>> We've heard people complaining about _git performance on IRC for a while
>> now. I have started to rewrite the _git file related completions some
>> time ago, but have since been swamped at work. So that has slowed down
>> to a halt.
>>
>> I'll attach the code to this mail though; maybe it'll be useful to
>> someone (search for "Git file listing helpers" to find the helper
>> functions). It doesn't have a helper for pathspecs yet, which the
>> git-checkout completion (and others) may need.
>>
>> Also, it's something I experimented with for only a short while. The
>> completions did work for me in my limited set of use-cases - they are
>> probably not perfect, yet. But they scaled well even on huge
>> repositories with many *many* files (like the linux kernel's git
>> repository).
>
>> Cc:ing Nikolai, too.
>
> I’ve been rewriting _git for a while now.  I’ve updated all the Main
> Porcelain Commands.  I’m currently stuck on something as unimportant
> as git-config, but I want to get everything right and I’m doing it all
> in man page order.  I’ll hopefully have a delayed Christmas gift for
> you all at the beginning of 2011.  I’ll take a look at your changes
> and integrate them if they are still applicable.
>
> My main problem right now is that I’m working off of the Debian Zsh
> Git repository where I don’t have write permissions.  I’d like to set
> up a Zsh Git repository at GitHub so that I can more easily distribute
> my changes, but I haven’t had time to look into setting this up.
> Perhaps someone can explain how you set up a CVS-to-Git mirror on
> GitHub?
>

That's easy.
1) create a project at github or any other git hoster and a plain git
repository in this project.
2) create a local git repo with 'git init', use git-cvsimport to
import the cvs repo into this git repo.
3) add the git hoster (i.e. github) as a remote in your git repo via
'git remote add' (or just copy'n'paste this from the hosters
description).
4) push the imported cvs repo, which is now your git repo, to the remote.

You can use git-cvsexportcommit to get it back into CVS.
You can also use git-cvsimport to get your git-repo up-to-date,
because I don't think there is a way that github itself can keep track
of an external CVS repo.

Hope this helps -- looking forward to the shiny new git-completion!


  parent reply	other threads:[~2010-12-10 11:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 22:06 Brett Simmers
2010-12-09 22:18 ` Benjamin R. Haskell
2010-12-10  0:10   ` Brett Simmers
     [not found]   ` <87k4jhsx78.fsf@ft.bewatermyfriend.org>
2010-12-10 11:37     ` Nikolai Weibull
2010-12-10 11:49       ` Frank Terbeck
2010-12-10 12:09         ` Nikolai Weibull
2010-12-10 11:54       ` Thomas Gstädtner [this message]
2010-12-10 12:11         ` Nikolai Weibull
2010-12-10 12:48   ` Oliver Kiddle
2010-12-10 14:00     ` Nikolai Weibull
2010-12-10 11:29 ` Nikolai Weibull

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimFeBgGqLRSyYMtdRR5scXByDm8EP2RHfgfjtgx@mail.gmail.com \
    --to=thomas@gstaedtner.net \
    --cc=now@bitwi.se \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).