Quoth the git-remote-helpers man page:
"If option check-connectivity is requested, the helper must output
connectivity-ok if the clone is self-contained and connected."
I tried doing that in a helper, but I still got a connectivity check.
Looking at the code, it looks like this only
Greetings My Dearest One.
My name is Mrs.Samira Hassim, i saw your profile and became interested
in you, please contact me through my email address
(sharmamrssandhya...@gmail.com) to know each other and i have
something very important to tell you, i wait for your response to my
email ID. (sharmamr
On Fri, May 03, 2019 at 04:18:02PM -0400, Jeffrey Walton wrote:
> I'm catching one failed self test under a sanitizer build. It looks
> like there's some latent UB present during 'make check'
How are you providing sanitizer options? If you're just putting
-fsanitize=undefined in the compiler flag
Hi Everyone,
I'm catching one failed self test under a sanitizer build. It looks
like there's some latent UB present during 'make check'
ok 39 - using --untracked-cache does not fail when core.untrackedCache is false
ok 40 - setting core.untrackedCache to keep
not ok 41 -
We annotated our test_must_fail calls in 8bf4becf0c (add "ok=sigpipe" to
test_must_fail and use it to fix flaky tests, 2015-11-27) because the
abrupt hangup of the server meant that we'd sometimes fail on read() and
sometimes get SIGPIPE on write().
But since 143588949c (fetch:
Được gửi từ thiết bị di động Huawei
Greetings
Can you please assist me to receive about 15 million Euros into your
personal account? . I will give you details as I hear from you.
Kindly send me the followings
Full Names
Address
Occupation
Direct Mobile Telephone Lines
Nationality
Regards,
Mr Ahmed Zama
Greetings,
I humbly solicit for your partnership to transfer €15 million Euros
into your personal or company’s account .I will offer you 30% of the
total sum,60% will be for me while 10% will set aside for expenses
that may be incurred on the process of transferring the fund. Contact
me for more d
Greetings
Compliment of the day to you. I am Mr Ahmed Zama, I am sending this
brief letter to solicit your partnership to transfer €15 million Euros
into your account for investment in your country. I shall send you
more information and procedures when I receive positive response from
you.
Thanks
Greetings,
I humbly solicit for your partnership to transfer €15 million Euros
into your personal or company’s account .Contact me for more detailed
explanation.
Kindly send me the followings
Full Names
Address
Occupation
Direct Mobile Telephone Lines
Nationality
Ahmed Zama
+22675844869
Greetings,
Can we discuss business here in the internet ? Contact me for more details.
Ahmed Zama
Greetings,
I humbly solicit for your partnership to transfer €15 million Euros
into your personal or company’s account .Contact me for more detailed
explanation.
Kindly send me the follwings
Full Names
Address
Occupation
Direct Mobile Telephone Lines
Nationality
Ahmed Zama
+22675844869
Functions like die_errno() use fmt_with_err() to combine the
caller-provided format with the strerror() string. We use a
fixed stack buffer because we're already handling an error
and don't have any way to report another one. Our buffer
should generally be big enough to fit this, but if it's not,
t
changed, 4 insertions(+), 1 deletion(-)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 7d620bf2a9a..926aefd1551 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -616,7 +616,7 @@ list_contains () {
# ok=[,<...>]:
# Don't treat an exit caused b
Dear Friend,
Please can both of us handle a lucrative deal.?? I will give you the
full detail explanation as soon as I hear from you.
Faithfully yours,
Mr Ahmed Zama
Dear Sir,
Please can both of us handle a lucrative deal.?? I will give you the
full detail explanation as soon as I hear from you.
Faithfully yours,
Mr Ahmed Zama
Dear Friend
I have a Beneficial Business Project for you worth €15 million Euros.
Reply me for more information.
Ahmed Zama
Greetings,
I am desperately in need of a foreigner with a foreign account. I have
a profitable business that wil be of a benefit to both of us. Permit
me to disclose the details of the business to you
Ahmed Zama
a
bug go unnoticed.
- - test_might_fail
+ Accepts the following options:
+
+ ok=[,<...>]:
+ Don't treat an exit caused by the given signal as error.
+ Multiple signals can be specified as a comma separated list.
+ Currently recognized signal names are: sigpipe, suc
On Tue, 26 Sep 2017 17:26:33 +0200
Michael Haggerty wrote:
> Maybe naming has been discussed at length before, and I am jumping into
> a long-settled topic. And admittedly this is bikeshedding.
>
> But I find these names obscure, even as a developer. And terms like this
> will undoubtedly bleed
Jonathan Tan writes:
> I've pushed a new version:
>
> https://github.com/jonathantanmy/git/tree/partialclone3
Just FYI, the reason why I commented only on the first patch in your
previous series at GitHub wasn't because I found the others perfect
and nothing to comment on. It was because I foun
On Fri, 15 Sep 2017 13:43:43 -0700
Jonathan Tan wrote:
> For those interested in partial clones and/or missing objects in repos,
> I've updated my original partialclone patches to not require an explicit
> list of promises. Fetch/clone still only permits exclusion of blobs, but
> the infrastructu
On Tue, 26 Sep 2017 10:25:16 -0400
Jeff Hostetler wrote:
> >> Perhaps you could augment the OID lookup to remember where the object
> >> was found (essentially a .promisor bit set). Then you wouldn't need
> >> to touch them all.
> >
> > Sorry - I don't understand this. Are you saying that missi
On 09/22/2017 12:42 AM, Jonathan Tan wrote:
> On Thu, 21 Sep 2017 13:57:30 Jeff Hostetler wrote:
> [...]
>> I struggled with the terms here a little when looking at the source.
>> () A remote responding to a partial-clone is termed a
>> "promisor-remote". () Packfiles received from a promisor-remo
On 9/22/2017 6:58 PM, Jonathan Tan wrote:
On Fri, 22 Sep 2017 17:32:00 -0400
Jeff Hostetler wrote:
I guess I'm afraid that the first call to is_promised() is going
cause a very long pause as it loads up a very large hash of objects.
Yes, the first call will cause a long pause. (I think fsc
doesn't have the size. It just knows it is missing and it
needs it. It doesn't matter why it is missing. (But I guess the client
could assume it is because it is large.)
Ah, OK.
So rev-list on the client could filter the objects it has by size.
My issue is that if the purpose of this
On Fri, 22 Sep 2017 17:32:00 -0400
Jeff Hostetler wrote:
> I guess I'm afraid that the first call to is_promised() is going
> cause a very long pause as it loads up a very large hash of objects.
Yes, the first call will cause a long pause. (I think fsck and gc can
tolerate this, but a better sol
doesn't have the size. It just knows it is missing and it
> needs it. It doesn't matter why it is missing. (But I guess the client
> could assume it is because it is large.)
Ah, OK.
> So rev-list on the client could filter the objects it has by size.
My issue is that if
On Fri, 22 Sep 2017 17:02:11 -0400
Jeff Hostetler wrote:
> > I was struggling a bit with the terminology, true.
> >
> > Right now I'm thinking of:
> > - promisor remote (as you defined)
> > - promisor packfile (as you defined)
> > - promisor object is an object known to belong to the promi
On 9/21/2017 7:04 PM, Jonathan Tan wrote:
On Thu, 21 Sep 2017 14:00:40 -0400
Jeff Hostetler wrote:
(part 3)
Additional overall comments on:
https://github.com/jonathantanmy/git/commits/partialclone2
{} WRT the code in is_promised() [1]
[1]
https://github.com/jonathantanmy/git/commit/7a9c2
at is true.
{} An early draft of this type of filtering is here [3]. I hope to
push up a revised draft of this shortly.
[3]
https://public-inbox.org/git/20170713173459.3559-1-...@jeffhostetler.com/
OK - I'll take a look when that is done (I think I commented on an
earlier version on that)
cond email with specific questions
and comments to keep this from being too long).
OK - thanks for your detailed comments.
I like that git-clone saves the partial clone settings in the
.git/config. This should make it easier for subsequent commands to
default to the right settings.
Do we allow
On Thu, 21 Sep 2017 14:00:40 -0400
Jeff Hostetler wrote:
> (part 3)
>
> Additional overall comments on:
> https://github.com/jonathantanmy/git/commits/partialclone2
>
> {} WRT the code in is_promised() [1]
>
> [1]
> https://github.com/jonathantanmy/git/commit/7a9c2d9b6e2fce293817b595dee29a7eed
d
> what to do with it. It would be difficult to add tree-trimming
> at this level, for example.
That is true.
> {} An early draft of this type of filtering is here [3]. I hope to
> push up a revised draft of this shortly.
>
> [3]
> https://public-inbox.org/git/20170713173459.3559-1-...@jeffhostetler.com/
OK - I'll take a look when that is done (I think I commented on an
earlier version on that).
; and comments to keep this from being too long).
OK - thanks for your detailed comments.
> I like that git-clone saves the partial clone settings in the
> .git/config. This should make it easier for subsequent commands to
> default to the right settings.
>
> Do we allow a partial-
(part 3)
Additional overall comments on:
https://github.com/jonathantanmy/git/commits/partialclone2
{} WRT the code in is_promised() [1]
[1]
https://github.com/jonathantanmy/git/commit/7a9c2d9b6e2fce293817b595dee29a7eede0#diff-5d5d5dc185ef37dc30bb7d9a7ae0c4e8R1960
{} it looked like it
(part 2)
Additional overall comments on:
https://github.com/jonathantanmy/git/commits/partialclone2
{} I think it would help to split the blob-max-bytes filtering and the
promisor/promised concepts and discuss them independently.
{} Then we can talk about about the promisor/promised funct
There's a lot in this patch series. I'm still studying it, but here
are some notes and questions. I'll start with direct responses to
the RFC here and follow up in a second email with specific questions
and comments to keep this from being too long).
On 9/15/2017 4:43 PM, Jonathan Tan wrote:
Jonathan Tan writes:
> For those interested in partial clones and/or missing objects in repos,
> I've updated my original partialclone patches to not require an explicit
> list of promises. Fetch/clone still only permits exclusion of blobs, but
> the infrastructure is there for a local repo to su
For those interested in partial clones and/or missing objects in repos,
I've updated my original partialclone patches to not require an explicit
list of promises. Fetch/clone still only permits exclusion of blobs, but
the infrastructure is there for a local repo to support missing trees
and commits
e/stable and I get this
> >> error (tests upto this succeeds).
> >>
> >> not ok 32 - should avoid cleaning possible submodules
> >
> > How about re-running the script with -i -v -x? If the output is still
> > not shining enough light on it, maybe you wa
On 2016, ജൂൺ 7 9:16:01 PM IST, Stefan Beller wrote:
>On Tue, Jun 7, 2016 at 8:43 AM, Stefan Beller
>wrote:
>> (Are you telling me that patch is faulty?)
>
>The patch is not part of v2.8.1 but part of v2.8.3,
>so take a later version, or cherry-pick that patch manually.
Thanks! I have ignored t
On Tue, Jun 7, 2016 at 8:43 AM, Stefan Beller wrote:
> (Are you telling me that patch is faulty?)
The patch is not part of v2.8.1 but part of v2.8.3,
so take a later version, or cherry-pick that patch manually.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a mes
http://thread.gmane.org/gmane.comp.version-control.git/293025
TL;DR: don't run tests as root, or cherry-pick
cadfbef98032fbc6874b5efd70d1e33dbeb4640d
(Are you telling me that patch is faulty?)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@
On Tuesday 07 June 2016 04:00 PM, Johannes Schindelin wrote:
> Hi Pirate Praveen,
>
> On Tue, 7 Jun 2016, Pirate Praveen wrote:
>
>> I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this
>> error (tests upto this succeeds).
>>
>> n
Hi Pirate Praveen,
On Tue, 7 Jun 2016, Pirate Praveen wrote:
> I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this
> error (tests upto this succeeds).
>
> not ok 32 - should avoid cleaning possible submodules
How about re-running the script with -i -v -x?
Hi,
I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this
error (tests upto this succeeds).
not ok 32 - should avoid cleaning possible submodules
I added debian stretch repo to apt sources.list and ran apt-get source
-b git.
You can see the build options passed here
My greeting to you over there and i hope all is fine, how are you doing, please
my dear i saw your profile on FB and i
became interested to know more about you, and i hope it will be the same from
you, please i will like you to contact me
to my email so that i will tell you more about me below,(
These were added by 8bf4bec (add "ok=sigpipe" to
test_must_fail and use it to fix flaky tests, 2015-11-27)
because we would racily die via SIGPIPE when the pack was
rejected by the other side.
But since we have recently de-flaked send-pack, we should be
able to tighten up these tests
On 28 Nov 2015, at 18:10, Jeff King wrote:
> On Fri, Nov 27, 2015 at 10:15:14AM +0100, larsxschnei...@gmail.com wrote:
>
>> From: Lars Schneider
>>
>> t5516 "75 - deny fetch unreachable SHA1, allowtipsha1inwant=true" is
>> flaky in the following case:
>> 1. remote upload-pack finds out "not o
On Fri, Nov 27, 2015 at 10:15:14AM +0100, larsxschnei...@gmail.com wrote:
> From: Lars Schneider
>
> t5516 "75 - deny fetch unreachable SHA1, allowtipsha1inwant=true" is
> flaky in the following case:
> 1. remote upload-pack finds out "not our ref"
> 2. remote sends a response and closes the pip
d-pack
4. write call in wrapper.c dies with SIGPIPE
t5504 "9 - push with transfer.fsckobjects" is flaky, too, and returns
SIGPIPE once in a while. I had to remove the final "To dst..." output
check because there is no output if the process dies with SIGPUPE.
Accept such a d
d-pack
4. write call in wrapper.c dies with SIGPIPE
t5504 "9 - push with transfer.fsckobjects" is flaky, too, and returns
SIGPIPE once in a while. I had to remove the final "To dst..." output
check because there is no output if the process dies with SIGPUPE.
Accept such a d
d-pack
4. write call in wrapper.c dies with SIGPIPE
t5504 "9 - push with transfer.fsckobjects" is flaky, too, and returns
SIGPIPE once in a while. I had to remove the final "To dst..." output
check because there is no output if the process dies with SIGPUPE.
Accept such a d
+Paul Tan who rewrote git pull in C recently.
The manpage:
-u, --update-head-ok
By default git fetch refuses to update the head which
corresponds to the current branch. This flag disables the check. This
is purely for the internal use for git pull to communicate with
git
According to the documentation these options are supported:
$ git help pull | grep -e '--update-head-ok'
-u, --update-head-ok
However:
$ git pull --update-head-ok
error: unknown option `update-head-ok'
Using:
$ git --version
git version 2.6.1
$ pacman --query --info git
Hi Junio,
On 2015-06-29 07:42, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
>> Hmm. Maybe we should still warn when there is no empty line finishing
>> the header explicitly, or at least make it FSCK_IGNORE by default so
>> that maintainers who like a stricter check can upgrade the cond
Johannes Schindelin writes:
>> +/*
>> + * We did not find double-LF that separates the header
>> + * and the body. Not having a body is not a crime but
>> + * we do want to see the terminating LF for the last header
>> + * line.
>> + */
>> +if (size && buffer[size - 1
Hi Junio,
On 2015-06-28 20:18, Junio C Hamano wrote:
> diff --git a/fsck.c b/fsck.c
> index 88c92e8..3f264e7 100644
> --- a/fsck.c
> +++ b/fsck.c
> @@ -255,6 +255,15 @@ static int require_end_of_header(const void
> *data, unsigned long size,
> }
> }
>
> + /*
> + * We
On Sun, Jun 28, 2015 at 2:18 PM, Junio C Hamano wrote:
> When fsck validates a commit or a tag object, it scans each line in
> the header the object using helper functions such as "start_with()",
s/header/& of/
> etc. that work on a NUL terminated buffer, but before a1e920a0
> (index-pack: termi
When fsck validates a commit or a tag object, it scans each line in
the header the object using helper functions such as "start_with()",
etc. that work on a NUL terminated buffer, but before a1e920a0
(index-pack: terminate object buffers with NUL, 2014-12-08), the
validation functions were fed the
test_ok_ () {
test_success=$(($test_success + 1))
- say_color "" "${statusprefix}ok $test_count - $@"
+ say_color "" "ok $test_count - $@"
}
test_failure_ () {
test_failure=$(($test_failure + 1))
- say_color error "${status
'$1'" >&2; exit 1 ;;
esac
@@ -316,12 +319,12 @@ trap 'die' EXIT
test_ok_ () {
test_success=$(($test_success + 1))
- say_color "" "ok $test_count - $@"
+ say_color "" "${statusprefix}ok $test_count - $@&q
'$1'" >&2; exit 1 ;;
esac
@@ -316,12 +319,12 @@ trap 'die' EXIT
test_ok_ () {
test_success=$(($test_success + 1))
- say_color "" "ok $test_count - $@"
+ say_color "" "${statusprefix}ok $test_count - $@&q
'$1'" >&2; exit 1 ;;
esac
@@ -316,12 +319,12 @@ trap 'die' EXIT
test_ok_ () {
test_success=$(($test_success + 1))
- say_color "" "ok $test_count - $@"
+ say_color "" "${statusprefix}ok $test_count - $@&q
un.
>>
>> Maybe we do not care about standards for this library or for your
>> use-case, but placing this prefix before the "{ok,not ok}" breaks the
>> TAProtocol.
>> http://podwiki.hexten.net/TAP/TAP.html?page=TAP
>>
>> Maybe you can put the prefix
your
> use-case, but placing this prefix before the "{ok,not ok}" breaks the
> TAProtocol.
> http://podwiki.hexten.net/TAP/TAP.html?page=TAP
>
> Maybe you can put the prefix _after_ the "{ok, not ok}" and test number.
Actually that was half on purpose. You will
re the "{ok,not ok}" breaks the
TAProtocol.
http://podwiki.hexten.net/TAP/TAP.html?page=TAP
Maybe you can put the prefix _after_ the "{ok, not ok}" and test number.
Phil
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majo
ix=$(expr "z$1" : 'z[^=]*=\(.*\)')
+ shift ;;
*)
echo "error: unknown test option '$1'" >&2; exit 1 ;;
esac
@@ -316,12 +319,12 @@ trap 'die' EXIT
test_ok_ () {
test_success=$(($test_success + 1))
- say_color
From: Adam Spiers
The old output to say "not ok - 1 messsage" was working by accident
only because the test numbers are optional in TAP.
Signed-off-by: Adam Spiers
Signed-off-by: Junio C Hamano
---
t/t-basic.sh | 4 ++--
t/test-lib.sh| 2 +-
2 files changed, 3 insert
The old output to say "not ok - 1 messsage" was working by accident
only because the test numbers are optional in TAP.
Signed-off-by: Adam Spiers
---
t/t-basic.sh | 4 ++--
t/test-lib.sh| 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/t/t-basic.sh
'/home/jrn/.config/git/config': Not a directory
warning: unable to access '/home/jrn/.config/git/config': Not a directory
warning: unable to access '/home/jrn/.config/git/config': Not a directory
Compare v1.7.12.1~2^2 (attr:failure to open a .gitattributes file
is OK w
On Thu, Sep 20, 2012 at 12:39 AM, Junio C Hamano wrote:
> Adam Spiers writes:
>
>> Signed-off-by: Adam Spiers
>> ---
>> t/t-basic.sh | 4 ++--
>> t/test-lib.sh| 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>
>> mode change 100644 => 100755 t/test-lib.sh
>
> Peff might have
Adam Spiers writes:
> Signed-off-by: Adam Spiers
> ---
> t/t-basic.sh | 4 ++--
> t/test-lib.sh| 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
> mode change 100644 => 100755 t/test-lib.sh
Peff might have already pointed out, but this is wrong. Will queue
with an obvious t
On Wed, Sep 19, 2012 at 06:15:11PM +0100, Adam Spiers wrote:
> test_failure_ () {
> test_failure=$(($test_failure + 1))
> - say_color error "not ok - $test_count $1"
> + say_color error "not ok $test_count - $1"
Interesting. I wondered what TAP ha
000-basic.sh
@@ -167,13 +167,13 @@ test_expect_success 'tests clean up even on failures' "
! test -s err &&
! test -f \"trash directory.failing-cleanup/clean-after-failure\" &&
sed -e 's/Z$//' -e 's/^> //' >expec
Make cg-commit aware of the rename of git-write-tree --no-check to --missing-ok.
Signed-off-by: Bryan Larsen <[EMAIL PROTECTED]>
---
diff --git a/cg-commit b/cg-commit
--- a/cg-commit
+++ b/cg-commit
@@ -111,13 +111,13 @@ forceeditor=
ignorecache=
infoonly=
commitalways=
-nocheck=
+mis
Add --missing-ok option to git-write.tree. This option allows a write-tree
even if the referenced objects are not in the database.
Signed-off-by: Bryan Larsen <[EMAIL PROTECTED]>
---
diff --git a/Documentation/git-write-tree.txt b/Documentation/git-write-tree.txt
--- a/Documentation/git
one that Joel Becker
found, plus the -N option needs to be passed to cg-commit.
Finally, Junio suggested that the --no-check option be renamed to
--missing-ok.
These patches fix the situation up.
1/4: bugfix for cg-init ARGV
2/4: bugfix for cg-init.
3/4: add --missing-ok option to git-write-tree
Dear diary, on Thu, Apr 21, 2005 at 03:55:26PM CEST, I got a letter
where Steven Cole <[EMAIL PROTECTED]> told me that...
> Executive summary: I received some alarming errors while doing
> a git pull of the latest kernel from kernel.org, but it appears
> that all is well. Continue reading for the
fstat patch-2.6.12-rc3 | tail -n 2
sound/usb/usx2y/usbusx2yaudio.c |1
4622 files changed, 271839 insertions(+), 156792 deletions(-)
Despite the errors from the "git pull", the files look OK.
Steven
-
To unsubscribe from this list: send the line "unsubscri
81 matches
Mail list logo
