On 2015-02-28 02.01, Stefan Beller wrote:
If this is over git protocol, the flags is appended as the next
parameter after host=. If it's ssh, a new argument is appended to the
command line.
None of the callers use this now though.
[sb: originally by pclouds, rebased as jk implemented
On Sat, Feb 28, 2015 at 2:19 PM, Mårten Kongstad
marten.kongs...@gmail.com wrote:
[...]
Signed-off-by: Mårten Kongstad marten.kongs...@gmail.com
Acked-by: Johan Herland jo...@herland.net
--
Johan Herland, jo...@herland.net
www.herland.net
--
To unsubscribe from this list: send the line
On Sat, Feb 28, 2015 at 2:47 PM, Kyle J. McKay mack...@gmail.com wrote:
On Feb 27, 2015, at 17:01, Stefan Beller wrote:
From: Nguyễn Thái Ngọc Duy pclo...@gmail.com
The only difference from the original protocol client capabilities are
negotiated before initial refs advertisment.
Client
On Sat, Feb 28, 2015 at 8:01 AM, Stefan Beller sbel...@google.com wrote:
Notes:
v1:
I am still undecided if the client should then accept/resend
the capabilities to confirm them, which would make the client the
ultimate decider which capabilities are used.
My gut feeling
Signed-off-by: Jean-Noel Avila jn.av...@free.fr
---
builtin/clean.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/builtin/clean.c b/builtin/clean.c
index 7e7fdcf..2c98661 100644
--- a/builtin/clean.c
+++ b/builtin/clean.c
@@ -754,6 +754,9 @@ static int ask_each_cmd(void)
When --shortstat is used in conjunction with --dirstat=changes, git diff will
output the dirstat information twice: first as calculated by the 'lines'
algorithm, then as calculated by the 'changes' algorithm:
$ git diff --dirstat=changes,10 --shortstat v2.2.0..v2.2.1
23 files changed,
On Sat, Feb 28, 2015 at 4:18 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Notice that with recent Git versions, ofs-delta objects are
preferred over ref-delta objects and ref-delta objects have no reason
to be present in a clone pack.
It is
On Sat, Feb 28, 2015 at 8:01 AM, Stefan Beller sbel...@google.com wrote:
diff --git a/Documentation/technical/protocol-capabilities.txt
b/Documentation/technical/protocol-capabilities.txt
index 4f8a7bf..40ddb37 100644
--- a/Documentation/technical/protocol-capabilities.txt
+++
Attn My Dear
I have registered your package with BCEAO BANK PLC Republic of Togo
this morning and we agreed up that the delivery of your $2.8m in ATM
CARD delivery will take place Tomorrow morning call me
+234-070-313-564-01 your information is needed
Full Name:
Home Address
occupation:
Cell
Hi,
TL;DR: Let's define a standard for embedding stronger checksums in tags and
commit messages:
https://github.com/cgwalters/homegit/blob/master/bin/git-evtag
I think tarballs should go away as a source distribution mechanism in favor of
pure git. I won't go into too many details of the why
Hi, the scenario is as follows: I'm working on a repo where only
rebase is used and never merge (which can arguably be a bad
thing). Anyway, I worked on a separate branch for some time and now I
need to integrate all the changes introduces by master (and prepare
some fixup commits that will be
On Feb 28, 2015, at 03:22, Duy Nguyen wrote:
The client should only trigger this behavior when it knows the server
can deal with it. And that is possible because in the last fetch, the
server has told the client that it's capable of receiving this
capabilities argument. Backward compatibility
2015-02-28 23:39 GMT+08:00 Jean-Noel Avila jn.av...@free.fr:
Signed-off-by: Jean-Noel Avila jn.av...@free.fr
---
builtin/clean.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/builtin/clean.c b/builtin/clean.c
index 7e7fdcf..2c98661 100644
--- a/builtin/clean.c
+++
On Thu, Feb 26, 2015 at 3:14 PM, Christoph Anton Mitterer
cales...@scientia.net wrote:
I saw that when plain git (i.e. git://) is used, the client tells the
server the hostname specified on the client side.
For http one has the same automatically via http's Host: header.
But after watching
On Sun, Mar 1, 2015 at 5:36 AM, Kyle J. McKay mack...@gmail.com wrote:
On Feb 28, 2015, at 03:22, Duy Nguyen wrote:
The client should only trigger this behavior when it knows the server
can deal with it. And that is possible because in the last fetch, the
server has told the client that it's
2015-03-01 8:18 GMT+08:00 Jiang Xin worldhello@gmail.com:
2015-02-28 23:39 GMT+08:00 Jean-Noel Avila jn.av...@free.fr:
Signed-off-by: Jean-Noel Avila jn.av...@free.fr
---
builtin/clean.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/builtin/clean.c b/builtin/clean.c
index
Is there a point to including a different checksum inside
a git tag? If someone can break the SHA-1 checksum
in the repository then the recorded SHA-256 checksum can
be changed. In other words, wouldn't you be just as well
off handing someone a SHA-1 commit id?
If you can guard the SHA-256 with
On Sat, Feb 28, 2015 at 09:48:05AM -0500, Colin Walters wrote:
The above strawman code allows embedding the SHA256(git archive | tar). Now,
in order to make this work, the byte output of git archive must never change
in the
future. I'm not sure how valid an assumption this is. Timestamps are
Johan Herland jo...@herland.net writes:
On Sat, Feb 28, 2015 at 2:19 PM, Mårten Kongstad
marten.kongs...@gmail.com wrote:
[...]
Signed-off-by: Mårten Kongstad marten.kongs...@gmail.com
Acked-by: Johan Herland jo...@herland.net
Interesting. So nobody in real life uses --dirstat and
Stefan Beller sbel...@google.com writes:
Before 73bb33a (daemon: Strictly parse the extra arg part of the
command - 2009-06-04) a client sending extra arguments could DoS
git-daemon. 73bb33a fixed it by forbidding extra arguments.
Allow arguments other than host= again as a preparation step
When --shortstat is used in conjunction with --dirstat=changes, git diff will
output the dirstat information twice: first as calculated by the 'lines'
algorithm, then as calculated by the 'changes' algorithm:
$ git diff --dirstat=changes,10 --shortstat v2.2.0..v2.2.1
23 files changed,
Trevor Saunders tbsau...@tbsaunde.org writes:
There have been cases where I wanted grep to always ignore certain
files, but to still get text diffs for those files. One case is people
insist on using ChangeLog files, and another is people who commit
generated files of one sort or
Stefan Beller sbel...@google.com writes:
If this is over git protocol, the flags is appended as the next
parameter after host=. If it's ssh, a new argument is appended to the
command line.
None of the callers use this now though.
Replace some flags with something more meaningful, so that
Duy Nguyen pclo...@gmail.com writes:
Probably Not so ancient versions of Git tries to use ofs-delta
encoding whenever possible, so it is expected that objects encoded
using ref-delta are minority may be closer to the truth. And that
observation does justify why using two separate pools (one
Jiang Xin worldhello@gmail.com writes:
2015-02-28 23:39 GMT+08:00 Jean-Noel Avila jn.av...@free.fr:
Signed-off-by: Jean-Noel Avila jn.av...@free.fr
---
builtin/clean.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/builtin/clean.c b/builtin/clean.c
index 7e7fdcf..2c98661
Signed-off-by: Anders Kaseorg ande...@mit.edu
---
t/t5516-fetch-push.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
index 85c7fec..594d7a6 100755
--- a/t/t5516-fetch-push.sh
+++ b/t/t5516-fetch-push.sh
@@ -238,7 +238,7 @@
'was_alias' variable does not need to store it's value each iteration in the
loop, anyway this variable changes it's value with run_argv. So it does not
need to be static.
Signed-off-by: Alexander Kuleshov kuleshovm...@gmail.com
---
git.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
27 matches
Mail list logo
