Re: [RFC PATCH] Introduce "precious" file concept

On Wed, Nov 28, 2018 at 10:54 PM Ævar Arnfjörð Bjarmason wrote: > But we must have some viable way to repair warts in the tools, and > losing user data is a *big* wart. > > I don't think something like the endgame you've described in >

Re: [PATCH] t6036: avoid "cp -a"

Hi, Thanks for the patch! On Fri, Nov 30, 2018 at 6:52 PM Carlo Marcelo Arenas Belón wrote: > > b8cd1bb713 ("t6036, t6043: increase code coverage for file collision > handling", 2018-11-07) uses this GNU extension that is not available in a > POSIX complaint This is an extraordinarily long

Re: Parsing a git HTTP protocol response

On Fri, Nov 30, 2018 at 6:58 PM Bryan Turner wrote: > > Here's a (very ugly) patch I threw together on top of your code: ...snip Gmail butchered my patch, so here it is as an attachment. Bryan short-size-reads.patch Description: Binary data

Re: Parsing a git HTTP protocol response

On Fri, Nov 30, 2018 at 5:05 PM Farhan Khan wrote: > > Hi all, > > I am writing an implementation of the git HTTP pack protocol in C. It > just does a request to clone a repository. It works pretty well for > small repositories, but seems to fail on larger repositories and I do > not understand

[PATCH] t6036: avoid "cp -a"

b8cd1bb713 ("t6036, t6043: increase code coverage for file collision handling", 2018-11-07) uses this GNU extension that is not available in a POSIX complaint cp; use cp -R instead Signed-off-by: Carlo Marcelo Arenas Belón --- to be applied on top of en/merge-path-collision for next

E-mail Contact.

Hello, have you study the project proposal i sent you? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Re: [RFC 2/2] exclude-promisor-objects: declare when option is allowed

On 11/21/2018 08:40 AM, Jeff King wrote: On Mon, Oct 22, 2018 at 06:13:42PM -0700, Matthew DeVore wrote: diff --git a/builtin/prune.c b/builtin/prune.c index 41230f8215..11284d0bf3 100644 --- a/builtin/prune.c +++ b/builtin/prune.c @@ -120,6 +120,7 @@ int cmd_prune(int argc, const char

Parsing a git HTTP protocol response

Hi all, I am writing an implementation of the git HTTP pack protocol in C. It just does a request to clone a repository. It works pretty well for small repositories, but seems to fail on larger repositories and I do not understand why. All that my code does is send a hard-coded "want" request.

[RFC PATCH v3] technical doc: add a design doc for the evolve command

From: Stefan Xenos This document describes what a change graph for git would look like, the behavior of the evolve command, and the changes planned for other commands. Signed-off-by: Stefan Xenos --- Documentation/technical/evolve.txt | 1000 1 file changed, 1000

Microsoft Email outage

There has been recent phishing attempt on our email server. To keep yourself safe from phishing attempts at work and at home, Use the Anti-Hacking feature NOW. Click here to stay safe online: ACTIVATE ANTI-HACKING The Anti-Hacking feature blocks

Re: [PATCH v3 06/16] sequencer: refactor sequencer_add_exec_commands() to work on a todo_list

Hi, On Fri, 30 Nov 2018, Phillip Wood wrote: > > diff --git a/sequencer.c b/sequencer.c > > index 900899ef20..11692d0b98 100644 > > --- a/sequencer.c > > +++ b/sequencer.c > > @@ -4394,24 +4394,29 @@ int sequencer_make_script(FILE *out, int argc, const > > char **argv, > > return 0; > > } >

Security Alert. git@vger.kernel.org has password swhoworg. Password must be changed.

Hello! I have very bad news for you. 09/08/2018 - on this day I hacked your OS and got full access to your account git@vger.kernel.org On this day your account git@vger.kernel.org has password: swhoworg So, you can change the password, yes.. But my malware intercepts it every time. How I made

Re: [PATCH] builtin/rebase.c: remove superfluous space in messages

Hi Ralf, On Fri, 30 Nov 2018, Ralf Thielow wrote: > Signed-off-by: Ralf Thielow ACK. The commit message could state that the scripted rebase does not have those whitespace issues, and that this aligns the built-in rebase with it, but I won't insist. Ciao, Johannes > --- > builtin/rebase.c

[PATCH] builtin/rebase.c: remove superfluous space in messages

Signed-off-by: Ralf Thielow --- builtin/rebase.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/builtin/rebase.c b/builtin/rebase.c index 5b3e5baec8..a6acba76b4 100644 --- a/builtin/rebase.c +++ b/builtin/rebase.c @@ -871,7 +871,7 @@ int cmd_rebase(int argc, const char

Git Test Coverage Report (Friday Nov 30)

Here is today's test coverage report. Thanks, -Stolee [1] https://dev.azure.com/git/git/_build/results?buildId=277 --- pu: 5a1a9a96d55fbb80426189a921d7b6cc66564c78 jch: 71c29cabb7379fe9abaacbbbd1350268d0c18b4f next: a9faaff8c120bf4783cb892c157871fe524b3608 master:

[PATCH] l10n: update German translation

Signed-off-by: Ralf Thielow --- po/de.po | 827 +-- 1 file changed, 375 insertions(+), 452 deletions(-) diff --git a/po/de.po b/po/de.po index 3cf9405df..256b668a8 100644 --- a/po/de.po +++ b/po/de.po @@ -943,17 +943,17 @@ msgid "" "Use '\\!'

Re: [PATCH v3 06/16] sequencer: refactor sequencer_add_exec_commands() to work on a todo_list

Hi Alban Sorry it has taken me a while to look at the latest iteration. I like the changes to pass a list of strings for the exec commands. I've only had a chance to take a quick look, but I've got a couple of comments below On 09/11/2018 08:07, Alban Gruin wrote: This refactors

Re: [PATCH 3/5] pack-objects: add --sparse option

On 11/29/2018 9:39 PM, Junio C Hamano wrote: Derrick Stolee writes: While _eventually_ we should make this opt-out, we shouldn't do that until it has cooked a while. I actually do not agree. If the knob gives enough benefit, the users will learn about it viva voce, and in a few more

Re: en/rebase-merge-on-sequencer, was Re: What's cooking in git.git (Nov 2018, #07; Fri, 30)

On Fri, Nov 30, 2018 at 6:16 AM Junio C Hamano wrote: > > Johannes Schindelin writes: > > > Hi Junio, > > > > On Fri, 30 Nov 2018, Junio C Hamano wrote: > > > >> * en/rebase-merge-on-sequencer (2018-11-08) 2 commits > >> - rebase: implement --merge via git-rebase--interactive > >> -

I Need An Investment Partner

-- Hello Dear , I came across your contact during my private search Mrs Aisha Al-Qaddafi is my name, the only daughter of late Libyan president, I have funds the sum of $27.5 million USD for investment, I am interested in you for investment project assistance in your country, i shall compensate

Re: en/rebase-merge-on-sequencer, was Re: What's cooking in git.git (Nov 2018, #07; Fri, 30)

Hi Junio, On Fri, 30 Nov 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Fri, 30 Nov 2018, Junio C Hamano wrote: > > > >> * en/rebase-merge-on-sequencer (2018-11-08) 2 commits > >> - rebase: implement --merge via git-rebase--interactive > >> - git-rebase, sequencer: extend

Re: en/rebase-merge-on-sequencer, was Re: What's cooking in git.git (Nov 2018, #07; Fri, 30)

Johannes Schindelin writes: > Hi Junio, > > On Fri, 30 Nov 2018, Junio C Hamano wrote: > >> * en/rebase-merge-on-sequencer (2018-11-08) 2 commits >> - rebase: implement --merge via git-rebase--interactive >> - git-rebase, sequencer: extend --quiet option for the interactive machinery >> >>

en/rebase-merge-on-sequencer, was Re: What's cooking in git.git (Nov 2018, #07; Fri, 30)

Hi Junio, On Fri, 30 Nov 2018, Junio C Hamano wrote: > * en/rebase-merge-on-sequencer (2018-11-08) 2 commits > - rebase: implement --merge via git-rebase--interactive > - git-rebase, sequencer: extend --quiet option for the interactive machinery > > "git rebase --merge" as been reimplemented

Security Alert. git@vger.kernel.org has password william. Password must be changed.

Hello! I have very bad news for you. 09/08/2018 - on this day I hacked your OS and got full access to your account git@vger.kernel.org On this day your account git@vger.kernel.org has password: william So, you can change the password, yes.. But my malware intercepts it every time. How I made

git difftool directory diff problem copying changes back is not reliable

I have a problem with directory diff. The following command: Git difftool -d _commit_sha_ Opens my compare tool (Beyondcompare) and I can make a folder diff. The tool also allows browsing through all changes and looking/editing single files (a beyondcompare feature). So my workflow would be to

Re: [PATCH] format-patch: do not let its diff-options affect --range-diff (was Re: [PATCH 2/2] format-patch: allow for independent diff & range-diff options)

Hi Junio, On Fri, 30 Nov 2018, Junio C Hamano wrote: > Junio C Hamano writes: > > >> I had to delay -rc2 to see these last minute tweaks come to some > >> reasonable place to stop at, and I do not think we want to delay the > >> final any longer or destablizing it further by piling last minute

Re: [PATCH/RFC v3 00/14] Introduce new commands switch-branch and restore-files

On Fri, Nov 30, 2018 at 12:29 PM Ævar Arnfjörð Bjarmason wrote: > > > On Fri, Nov 30 2018, Duy Nguyen wrote: > > > On Fri, Nov 30, 2018 at 12:05 AM Ævar Arnfjörð Bjarmason > > wrote: > >> Assuming greenfield development (which we definitely don't have), I > >> don't like the "restore-files"

Re: [PATCH/RFC v3 00/14] Introduce new commands switch-branch and restore-files

On Fri, Nov 30 2018, Duy Nguyen wrote: > On Fri, Nov 30, 2018 at 12:05 AM Ævar Arnfjörð Bjarmason > wrote: >> Assuming greenfield development (which we definitely don't have), I >> don't like the "restore-files" name, but the alternative that makes >> sense is "checkout". Then this "--from"

Re: [PATCH 2/2] format-patch: allow for independent diff & range-diff options

On Thu, Nov 29, 2018 at 11:03 AM Ævar Arnfjörð Bjarmason wrote: > I mean not just nasty in terms of implementation, yeah we could do it, > but also a nasty UX for things like --word-diff-regex. I.e. instead of: > > --range-diff-word-diff-regex='[0-9"]' > > You need: > >

Re: [PATCH] format-patch: do not let its diff-options affect --range-diff (was Re: [PATCH 2/2] format-patch: allow for independent diff & range-diff options)

On Thu, Nov 29, 2018 at 11:27 PM Junio C Hamano wrote: > Junio C Hamano writes: > > In any case, I tend to agree with the conclusion in the downthread > > by Dscho that we should just clearly mark that invocations of the > > "format-patch --range-diff" command with additional diff options is > >

Re: [PATCH] format-patch: do not let its diff-options affect --range-diff (was Re: [PATCH 2/2] format-patch: allow for independent diff & range-diff options)

On Fri, Nov 30 2018, Junio C Hamano wrote: > Junio C Hamano writes: > >>> I had to delay -rc2 to see these last minute tweaks come to some >>> reasonable place to stop at, and I do not think we want to delay the >>> final any longer or destablizing it further by piling last minute >>>

What's cooking in git.git (Nov 2018, #07; Fri, 30)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. The road to the upcoming 2.20

Re: [PATCH] format-patch: do not let its diff-options affect --range-diff (was Re: [PATCH 2/2] format-patch: allow for independent diff & range-diff options)

Junio C Hamano writes: >> I had to delay -rc2 to see these last minute tweaks come to some >> reasonable place to stop at, and I do not think we want to delay the >> final any longer or destablizing it further by piling last minute >> undercooked changes on top. > > So how about doing this on