"Franck Bui-Huu" [off-list ref] writes:
quoted
So if you beat me to it, that would be great. Or if you have a better
idea, that would be also great. :-)
Well I'll try to start something, not sure to have a lot of time
though. Please contact me before starting anything, I would be sad to
write something for /dev/null again ;)
I do not necessarily think your effort were for /dev/null; for
example, I was hoping you defend [PATCH 3/3].
While it makes sense to make "tar-tree --remote" usable outside
a git managed repository, I think people expect the connection
to obey core.gitproxy if the command is run inside a repository
that has a configuration file.
Junio C Hamano wrote:
"Franck Bui-Huu" [off-list ref] writes:
quoted
quoted
So if you beat me to it, that would be great. Or if you have a better
idea, that would be also great. :-)
Well I'll try to start something, not sure to have a lot of time
though. Please contact me before starting anything, I would be sad to
write something for /dev/null again ;)
I do not necessarily think your effort were for /dev/null; for
example, I was hoping you defend [PATCH 3/3].
While it makes sense to make "tar-tree --remote" usable outside
a git managed repository, I think people expect the connection
to obey core.gitproxy if the command is run inside a repository
that has a configuration file.
If I remember correclty git now support (totally undocumented) per-user
configuration file, so one can have core.gitproxy even outside git
repository. Although some warning that you are running from outside
repository and configuration might be not what you want would be nice.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
2006/9/2, Junio C Hamano [off-list ref]:
"Franck Bui-Huu" [off-list ref] writes:
quoted
quoted
So if you beat me to it, that would be great. Or if you have a better
idea, that would be also great. :-)
Well I'll try to start something, not sure to have a lot of time
though. Please contact me before starting anything, I would be sad to
write something for /dev/null again ;)
I do not necessarily think your effort were for /dev/null; for
example, I was hoping you defend [PATCH 3/3].
Well, with a new git-archive-tree command, I thought it would make
sense to put the remote logic there and let the git-tar-tree be a
local command. But Rene has a different approach, please see his new
thread "Add git-archive-tree".
While it makes sense to make "tar-tree --remote" usable outside
a git managed repository, I think people expect the connection
to obey core.gitproxy if the command is run inside a repository
that has a configuration file.
Make sense.
--
Franck
--
VGER BF report: U 0.799618