Re: Git send-email not sending email patches as subsequent replies

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

Re: [PATCH v11 4/4] ls-remote: create '--sort' option

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

Re: [PATCH v2 0/4] Lazy-load trees when reading commit-graph

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

Re: [PATCH 0/6] Compute and consume generation numbers

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

Re: [PATCH v11 1/4] ref-filter: use "struct object_id" consistently

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

Re: [PATCH v7 03/14] commit-graph: add format document

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

Re: Git send-email not sending email patches as subsequent replies

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

Re: [PATCH v7 02/14] csum-file: refactor finalize_hashfile() method

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

Re: [PATCH v4 00/13] Serialized Git Commit Graph

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 >>

Hello friend, did your received my email?.

my message...

Re: Git Merge contributor summit notes

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

Witam potrzebuję Pilnej odpowiedzi, abyśmy mogli porozmawiać o ważnej sprawie

Re: [PATCH] git-svn: avoid warning on undef readline()

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

Re: [PATCH v2 0/4] Lazy-load trees when reading commit-graph

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

Re: [PATCH 4/3] Makefile: untangle DEVELOPER and -Werror

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

Re: [PATCH 0/6] Compute and consume generation numbers

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

Re: [PATCH 4/3] Makefile: untangle DEVELOPER and -Werror

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

Re: [PATCH 0/6] Compute and consume generation numbers

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

[PATCH v11 2/4] ref-filter: make ref_array_item allocation more consistent

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

[PATCH v11 4/4] ls-remote: create '--sort' option

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

[PATCH v11 3/4] ref-filter: factor ref_array pushing into its own function

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

[PATCH v11 1/4] ref-filter: use "struct object_id" consistently

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. ---

Re: [PATCH 3/3] ref-filter: factor ref_array pushing into its own function

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

Re: [PATCH 4/3] Makefile: untangle DEVELOPER and -Werror

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

business Proposal / Geschäftsvorschlag

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

Re: [PATCH] send-email: fix docs regarding storing password with git credential

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

[PATCH] send-email: simplify Gmail example in the documentation

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

Re: [PATCH 4/3] Makefile: untangle DEVELOPER and -Werror

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

Re: [RFC PATCH 00/19] object-store refactoring 3 (replace objects, main ref store)

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

wir bieten 2% Kredite

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

OK

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

Re: [RFC][PATCH] git-stash: convert git stash list to C builtin

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

Re: [RFC][PATCH] git-stash: convert git stash list to C builtin

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

Re: [PATCH v5 1/3] builtin/config: introduce `--default`

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 >>

Re: [PATCH v5 1/3] builtin/config: introduce `--default`

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

Re: [PATCH v6 2/2] builtin/config.c: support `--type=` as preferred alias for `--type`

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

Re: Is support for 10.8 dropped?

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

Re: [PATCH v2 4/4] Document the new color.* settings to colorize push errors/hints

On Fri, Apr 6, 2018 at 8:15 AM, Johannes Schindelin wrote: > On Fri, 6 Apr 2018, Eric Sunshine wrote: >> On Thu, Apr 5, 2018 at 6:48 PM, Johannes Schindelin >> wrote: >> > +color.advice.advice:: >> > + Use customized color for hints.

Re: [PATCH 13/19] refs: store the main ref store inside the repository struct

On Fri, Apr 6, 2018 at 7:21 PM, Stefan Beller wrote: > diff --git a/repository.h b/repository.h > @@ -26,6 +26,11 @@ struct repository { > + /* > +* The store in which the refs are hold. > +*/ s/hold/held/ Also, this comment is short enough to fit on

Re: [PATCH 06/19] refs: add repository argument to get_main_ref_store

On Fri, Apr 6, 2018 at 7:21 PM, Stefan Beller wrote: > Add a repository argument to allow the get_main_ref_store caller > to be more specific about which repository to handle. This is a small > mechanical change; it doesn't change the implementation to handle > repositories

Guten Morgen,

Nachricht des Absenders: /Guten Morgen, Es tut mir sehr leid, Ihnen diese Nachricht zu senden, die Sie heute von mir nicht erwartet haben. Bitte seien Sie nicht überrascht, meine Nachricht zu lesen, weil Sie der beabsichtigte Empfänger sind. Ich habe Ihre E-Mail-Adresse über ein