On Fri, Apr 6, 2018 at 10:20 PM, Igor Korot wrote:
>>> dyld: lazy symbol binding failed: Symbol not found: ___strlcpy_chk
>>> Referenced from: /usr/local/git/libexec/git-core/git
>>> Expected in: /usr/lib/libSystem.B.dylib
>>
>> It's not clear what installer you used? Was it the package from
>
On Fri, Apr 6, 2018 at 8:39 PM, Taylor Blau wrote:
> On Fri, Apr 06, 2018 at 03:04:53AM -0400, Eric Sunshine wrote:
>> Sorry for being such a stickler, but this is still too mushy. The
>> first two sentences are saying effectively the same thing. One or the
>> other should be dropped or they shoul
On Fri, Apr 6, 2018 at 8:49 PM, Taylor Blau wrote:
> On Fri, Apr 06, 2018 at 02:53:45AM -0400, Eric Sunshine wrote:
>> On Fri, Apr 6, 2018 at 2:30 AM, Taylor Blau wrote:
>> > +test_expect_success 'uses --default when missing entry' '
>> > + echo quux >expect &&
>> > + git config -f co
On Fri, Apr 6, 2018 at 8:58 PM, Taylor Blau wrote:
> On Fri, Apr 06, 2018 at 03:40:56AM -0400, Eric Sunshine wrote:
>> On Fri, Apr 6, 2018 at 2:53 AM, Eric Sunshine
>> wrote:
>> One other issue. If "git config --default ..." fails, the --unset line
>> will never be invoked, thus cleanup won't ha
On Tue, Apr 3, 2018 at 5:38 PM, Paul-Sebastian Ungureanu
wrote:
> On 25.03.2018 10:08, Eric Sunshine wrote:
>> On Sat, Mar 24, 2018 at 2:23 PM, Paul-Sebastian Ungureanu
>> wrote:
>>> diff --git a/git.c b/git.c
>>> @@ -466,6 +466,7 @@ static struct cmd_struct commands[] = {
>>> { "stage",
On Sat, Apr 7, 2018 at 4:56 AM, Eric Sunshine wrote:
> The existing git-stash requires a working directory:
>
> % git stash list
> fatal: not a git repository (or any of the parent directories): .git
> %
Correction on the error message:
% git stash list
fatal: git-stash cannot be used without a
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
Sehr geehrte Damen und Herren,
Sie brauchen Geld? Sie sind auf der suche nach einem Darlehnen? Seriös und
unkompliziert?
Dann sind Sie hier bei uns genau richtig.
Durch unsere jahrelange Erfahrung und kompetente Beratung sind wir
Europaweit tätig.
Wir bieten jedem ein GÜNSTIGES Darlehnen zu TOP K
On Sat, Apr 7, 2018 at 1:21 AM, Stefan Beller wrote: *
> diff --git a/repository.h b/repository.h
> index 09df94a472..2922d3a28b 100644
> --- a/repository.h
> +++ b/repository.h
> @@ -26,6 +26,11 @@ struct repository {
> */
> struct raw_object_store *objects;
>
> + /*
>
On Fri, Apr 6, 2018 at 11:42 PM, Jeff King wrote:
> On Tue, Apr 03, 2018 at 05:17:00PM +0200, Duy Nguyen wrote:
>
>> It's not that complex. With the EAGER_DEVELOPER patch removed, we can
>> have something like this where eager devs just need to put
>>
>> DEVOPTS = gentle no-suppression
>>
>> a
There is no need for use to manually call ‘git credential’ especially
as the interface isn’t super user-friendly and a bit confusing. ‘git
send-email’ will do that for them at the first execution and if the
password matches, it will be saved in the store.
Simplify the documentaion so it dosn’t in
2018-04-04 22:14 GMT+01:00 Jeff King :
> On the other hand, I'm not sure why we need to pre-seed here. Wouldn't
> it be sufficient to just issue a "git send-email", which would then
> prompt for the password? And then you'd input your generated token,
> which would get saved via the approve mechani
I have a business Proposal for you, contact me directly
This business has a cash involvement of $250,000,000.00
Anders Karlsson
Ich habe einen Geschäftsvorschlag für Sie, kontaktieren Sie mich direkt
Dieses Unternehmen hat eine Beteiligung von $ 250.000.000,00
- [] Anders Karlsson
On Sat, Apr 07 2018, Duy Nguyen wrote:
> On Fri, Apr 6, 2018 at 11:42 PM, Jeff King wrote:
>> On Tue, Apr 03, 2018 at 05:17:00PM +0200, Duy Nguyen wrote:
>>
>>> It's not that complex. With the EAGER_DEVELOPER patch removed, we can
>>> have something like this where eager devs just need to put
>>
Looks good to me.
Reviewed-by: Harald Nordgren
On Fri, Apr 6, 2018 at 9:27 PM, Derrick Stolee wrote:
> On 4/6/2018 2:59 PM, Jeff King wrote:
>>
>> In preparation for callers constructing their own ref_array
>> structs, let's move our own internal push operation into its
>> own function.
>>
>> W
From: Jeff King
Internally we store a "struct object_id", and all of our
callers have one to pass us. But we insist that they peel it
to its bare-sha1 hash, which we then hashcpy() into place.
Let's pass it around as an object_id, which future-proofs us
for a post-sha1 world.
---
builtin/tag.c
From: Jeff King
We have a helper function to allocate ref_array_item
structs, but it only takes a subset of the possible fields
in the struct as initializers. We could have it accept an
argument for _every_ field, but that becomes a pain for the
fields which some callers don't want to set initial
Create a '--sort' option for ls-remote, based on the one from
for-each-ref. This e.g. allows ref names to be sorted by version
semantics, so that v1.2 is sorted before v1.10.
Signed-off-by: Harald Nordgren
---
Notes:
Rebasing my patch on Jeff King's refatoring patches
Documentation/git-ls-
From: Jeff King
In preparation for callers constructing their own ref_array
structs, let's move our own internal push operation into its
own function.
While we're at it, we can replace REALLOC_ARRAY() with
ALLOC_GROW(), which should give the growth operation
amortized linear complexity (as oppos
Hello,
Derrick Stolee writes:
> This is the first of several "small" patches that follow the serialized
> Git commit graph patch (ds/commit-graph).
>
> As described in Documentation/technical/commit-graph.txt, the generation
> number of a commit is one more than the maximum generation number amo
On Sat, Apr 7, 2018 at 2:36 PM, Ævar Arnfjörð Bjarmason
wrote:
> Anyway, I see you've pushed a new version with DEVOPTS. I'll submit mine
> on top of that once your new version lands (unless you want to try to
> integrate it yourself).
Actually I think I'll just drop both EAGER_DEVELOPER and DEVO
Derrick Stolee writes:
> On 4/3/2018 2:03 PM, Brandon Williams wrote:
>> On 04/03, Derrick Stolee wrote:
>>> This is the first of several "small" patches that follow the serialized
>>> Git commit graph patch (ds/commit-graph).
>>>
>>> As described in Documentation/technical/commit-graph.txt, the
On Sat, Apr 07 2018, Duy Nguyen wrote:
> On Sat, Apr 7, 2018 at 2:36 PM, Ævar Arnfjörð Bjarmason
> wrote:
>> Anyway, I see you've pushed a new version with DEVOPTS. I'll submit mine
>> on top of that once your new version lands (unless you want to try to
>> integrate it yourself).
>
> Actually I
Derrick Stolee writes:
[...]
> On the Linux repository, performance tests were run for the following
> command:
>
> git log --graph --oneline -1000
>
> Before: 0.92s
> After: 0.66s
> Rel %: -28.3%
>
> Adding '-- kernel/' to the command requires loading the root tree
> for every c
On Fri, Apr 06, 2018 at 01:15:14PM +, Ævar Arnfjörð Bjarmason wrote:
> Change code in Git.pm that sometimes calls chomp() on undef to only do
> so the value is defined.
>
> This code has been chomping undef values ever since it was added in
> b26098fc2f ("git-svn: reduce scope of input record
Brandon Williams writes:
> On 03/26, Jeff Hostetler wrote:
[...]
>> All of these cases could be eliminated if the type/size were available
>> in the OID.
>>
>> Just a thought. While we are converting to a new hash it seems like
>> this would be a good time to at least discuss it.
>
> Echoing wh
my message...
Derrick Stolee writes:
> On 4/2/2018 10:46 AM, Jakub Narebski wrote:
>> Derrick Stolee writes:
> [...]
>> I see the FELINE-index as a stronger form of generation numbers (called
>> also level of the vertex / node), in that it allows to negative-cut even
>> more, pruning paths that are known to b
Derrick Stolee writes:
> From: Derrick Stolee
>
> If we want to use a hashfile on the temporary file for a lockfile, then
> we need finalize_hashfile() to fully write the trailing hash but also keep
> the file descriptor open.
>
> Do this by adding a new CSUM_HASH_IN_STREAM flag along with a fun
David Davis wrote:
> Hello, I have the following git send-email command:
>
> git send-email -5 --quiet --thread --no-chain-reply-to --compose
> --subject='Recent Base Prototype Changes Summary'
> --to=davisda...@google.com --from=davisda...@google.com
>
> It's sending emails but as 5 individual
Derrick Stolee writes:
> diff --git a/Documentation/technical/commit-graph-format.txt
> b/Documentation/technical/commit-graph-format.txt
> new file mode 100644
> index 00..ad6af8105c
> --- /dev/null
> +++ b/Documentation/technical/commit-graph-format.txt
> @@ -0,0 +1,97 @@
> +Git commit
On Sat, Apr 7, 2018 at 12:42 PM, Harald Nordgren
wrote:
> From: Jeff King
>
> Internally we store a "struct object_id", and all of our
> callers have one to pass us. But we insist that they peel it
> to its bare-sha1 hash, which we then hashcpy() into place.
> Let's pass it around as an object_id
On 4/7/2018 12:55 PM, Jakub Narebski wrote:
Currently I am at the stage of reproducing results in FELINE paper:
"Reachability Queries in Very Large Graphs: A Fast Refined Online Search
Approach" by Renê R. Veloso, Loïc Cerf, Wagner Meira Jr and Mohammed
J. Zaki (2014). This paper is available in
On 4/7/2018 2:40 PM, Jakub Narebski wrote:
Derrick Stolee writes:
[...]
On the Linux repository, performance tests were run for the following
command:
git log --graph --oneline -1000
Before: 0.92s
After: 0.66s
Rel %: -28.3%
Adding '-- kernel/' to the command requires lo
On Sat, Apr 7, 2018 at 12:42 PM, Harald Nordgren
wrote:
> Create a '--sort' option for ls-remote, based on the one from
> for-each-ref. This e.g. allows ref names to be sorted by version
> semantics, so that v1.2 is sorted before v1.10.
>
> Signed-off-by: Harald Nordgren
> ---
> diff --git a/Docu
David Davis wrote:
> I'm seeing 6 individual emails, how do I just see one email followed by 5
> email replies to the one? I don't want six individual emails.
The five email replies you want are still individual emails.
Emails are ALWAYS "individual", and reply emails simply have a
References: an
37 matches
Mail list logo
