Hi,
On Tue, 2 Aug 2005, Junio C Hamano wrote:
This may be controversial from the robustness standpoint, so I
am placing it in the proposed update queue first. Discussions
on the list very welcomed.
I'd vote against it: As of now, I can perfectly do
export PATH=$PATH:/whereever/my/git/is
Hi,
On Thu, 4 Aug 2005, Junio C Hamano wrote:
Johannes Schindelin [EMAIL PROTECTED] writes:
This may be controversial from the robustness standpoint, so I
am placing it in the proposed update queue first. Discussions
on the list very welcomed.
I'd vote against it: As of now, I can
Johannes Schindelin [EMAIL PROTECTED] writes:
I'd like to not being forced to install git. Scenario: I have an SSH
account on a remote machine. I am not root there, but I'd like to
synchronize my work with git. I can not install git.
Sorry, but now you completely lost me. You want git, you
On Thu, 4 Aug 2005, Johannes Schindelin wrote:
* Make git-init-db create an absolute minimum $GIT_DIR
structure itself, if the template directory is not available,
possibly with a warning.
This would be exactly what I'd like. Let git-init-db create
.git/objects/[0-9a-f]{2}/,
[EMAIL PROTECTED] writes:
... I seem to recall a patch to create subdirectories of
.git/refs on demand (needed for tags/v99/1). I'd say just
.git/objects/(everything), .git/refs, and .git/info.
Having thought about this a bit more, I am inclined to drop
this. I see the template mechanism to
Hi,
On Thu, 4 Aug 2005, Junio C Hamano wrote:
Oh, I see. Then the templates/Makefile building into
templates/blt and then installing if you say make install
approach I described earlier would hopefully work perfectly well
for you. Just like you tack the $src to your $PATH, you can
define
6 matches
Mail list logo
