On Thu, Aug 13, 2015 at 11:42:50AM -0400, Dave Borowitz wrote:
In my ideal world:
-smart_options would never be NULL, and would instead be called
options with a smart bit which is unset for dumb protocols.
-Command line option processing code in {fetch,clone,push}.c would set
fields in
On Thu, Aug 13, 2015 at 06:10:48PM +0200, Elia Pinto wrote:
2015-08-13 18:01 GMT+02:00 Torsten Bögershausen tbo...@web.de:
+
from
https://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0.2C_2.0_and_3.0
sslv2 and sslv3 are deprecated.
Should there be a motivation in the commit
On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote:
As we known, HTTP/2.0 has been released. All Git-Smart-HTTP are currently
implemented using HTTP/1.1.
Nit: It is HTTP/2.
Frequently used Git developers often feel Git HTTP protocol is not
satisfactory, slow and unstable.This is
On Sat, Jul 11, 2015 at 10:23:09AM -0700, Shawn Pearce wrote:
On Sat, Jul 11, 2015 at 12:00 AM, Ilari Liusvaara
ilari.liusva...@elisanet.fi wrote:
On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote:
Frequently used Git developers often feel Git HTTP protocol is not
satisfactory
On Wed, Apr 15, 2015 at 08:13:51PM +0530, Pirate Praveen wrote:
Q: Are the mosh principles relevant to other network applications?
We think so. The design principles that Mosh stands for are
conservative: warning the user if the state being displayed is out of
date, serializing and
On Mon, Dec 29, 2014 at 10:47:58AM +0100, Jiri Sevcik wrote:
The remote-fd expects the transport to pass half-closes. So you can't
close all at once.
Let there be pipes W and R and transport connection C.
- W-read should be closed after being passed to remote-fd.
- R-write should be
On Wed, Sep 10, 2014 at 03:29:00PM +0200, Jiri Sevcik wrote:
Hi!
I have problem with using git-remote-fd function. I create two local
pipes for communication for locally running process git pull. Then I
start git-upload-pack on remote side (this process is started in
different part of my code
On Wed, Jan 22, 2014 at 12:22:23PM +0100, Michael Haggerty wrote:
I just noticed that there are exactly four Git manpages with an AUTHOR
section and five with a DOCUMENTATION section:
These sections are inconsistent with the other manpages and seem
superfluous in a project that has, on the
On Fri, Dec 27, 2013 at 02:21:31PM -0800, Junio C Hamano wrote:
Konstantin Khomoutov flatw...@users.sourceforge.net writes:
The Git protocol does not implement it itself but you can channel it
over a TLS tunnel (via stunnel for instance). Unfortunately, this
means a specialized software
On Sun, Oct 06, 2013 at 12:42:36AM +, brian m. carlson wrote:
GSS-Negotiate authentication always requires a rewind with CURL.
The remote in question only supports Negotiate authentication, so
prompting for a password in this case isn't going to help. I'm probably
going to look into
On Tue, Jun 11, 2013 at 01:25:14PM -0300, Chico Sokol wrote:
Is there any official documentation of tree objets format? Are tree
objects encoded specially in some way? How can I parse the inflated
contents of a tree object?
Tree object consists of entries, each concatenation of:
- Octal mode
On Sun, Mar 24, 2013 at 02:31:33PM -0400, Jeff King wrote:
Fscking the incoming objects does work, but of course it comes at a cost
in the normal case (for linux-2.6, I measured an increase in CPU time
with index-pack --strict from ~2.5 minutes to ~4 minutes). And I think
it is probably
On Sun, Oct 07, 2012 at 09:57:56PM +0200, Ævar Arnfjörð Bjarmason wrote:
Has anyone started working on a next-gen Git protocol as a result of
this discussion? If not I thought I'd give it a shot if/when I have
time.
Unfortunately, client signaling the version is nasty to do in ways that
13 matches
Mail list logo
