From: Aaron Schrab <aaron@schrab.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Curious result from "git" completion
Date: Sun, 7 Apr 2013 18:41:12 -0400 [thread overview]
Message-ID: <20130407224112.GF27178@pug.qqx.org> (raw)
In-Reply-To: <130407113333.ZM525@torch.brasslantern.com>
At 11:33 -0700 07 Apr 2013, Bart Schaefer <schaefer@brasslantern.com> wrote:
>Background: I have my own CVS repository with a slightly customized
>zsh
>module. It has stuff that's it's not really appropriate to push up to
>sourceforge, e.g., Makefile changes to be able to compile the docs under
>obsolete versions of texinfo, and the like. I use it to pull sources
>onto some hosts where git is not installed and it's a hassle to arrange
>for it to be. I have a script that previously sync'd CVS at sourceforge
>into a local sandbox based on my repository, which I'm updating to base
>the remote repository on git. The sync depends on being able to do a
>multi-way diff against a clean tree that has no version control clutter,
>which until the cutover I would generate with "cvs export".
Another option for that may be to do a clone using the
--separate-git-dir option to store the information that would normally
be in .git someplace else. That would create a .git file at the top
level of the clone rather than the usual directory, so it wouldn't be
completely clean but it would be very small with just a pointer to the
actual repository location. That has the benefit that such a clone is
still completely usable with git commands.
prev parent reply other threads:[~2013-04-07 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:44 Bart Schaefer
2013-04-04 19:33 ` Nikolai Weibull
2013-04-05 15:19 ` Bart Schaefer
2013-04-05 17:26 ` Frank Terbeck
2013-04-05 17:54 ` [PATCH] _git: Handle zero defined aliases better Frank Terbeck
2013-04-05 20:06 ` Nikolai Weibull
2013-04-05 20:15 ` Frank Terbeck
2013-04-04 19:57 ` Curious result from "git" completion Frank Terbeck
2013-04-07 18:33 ` Bart Schaefer
2013-04-07 22:41 ` Aaron Schrab [this message]
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=20130407224112.GF27178@pug.qqx.org \
--to=aaron@schrab.com \
--cc=schaefer@brasslantern.com \
--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).