Re: git version 2.20.1.windows.1 throws file name too long in gitk

Hi Bret, On Thu, 18 Apr 2019, Bret Barkelew wrote: > This issue is now being reported by more users inside MS. I'll also > reach out to the Git for Windows advocacy group to see if they have > any ideas. > > I have not had time to figure out the inner workings of Tcl/Tk. Is > there any way to tur

[PATCH 2/2] builtin/verify-tag: do not omit gpg on --format

From: Santiago Torres The current implementation of git-verify-tag omits the gpg output when the --format flag is passed. This may not be useful to users that want to see the gpg output *and* --format the output of git verify-tag. Instead, respect the --raw flag or the default gpg output. Signed

[PATCH 1/2] builtin/tag: do not omit -v gpg out for --format

From: Santiago Torres The current implementation of git tag -v omits the gpg output when the --format flag is passed. This may not be useful to users that want to see the gpg output *and* --format the output of the git tag -v. Instead, pass the default gpg interface output if --format is specifie

[PATCH 0/2] tag verification: do not mute gpg output

From: Santiago Torres The default behavior of the tag verification functions used to quiet down the gpg output if --format was passed. The rationale for this was to avoid --format to be litterred by the gpg output. However, this may be unnecessary because the gpg output is already streamed to std

[PATCH 2/2] format-patch: teach format.notes config option

In git-format-patch, notes can be appended with the `--notes` option. However, this must be specified by the user on an invocation-by-invocation basis. If a user is not careful, it's possible that they may forget to include it and generate a patch series without notes. Teach git-format-patch the `

[PATCH 1/2] git-format-patch.txt: document --no-notes option

Internally, git-format-patch uses the `handle_revision_opt` parser. The parser handles the `--no-notes` option to negate an earlier `--notes` option, but it isn't documented. Document this option so that users are aware of it. Signed-off-by: Denton Liu --- Documentation/git-format-patch.txt | 4

[PATCH 0/2] format-patch: teach format.notes config option

If a user sends patches with git-format-patch, they might want to take advantage of notes to add additional commentary. However, if they are forgetful (like me) they may forget to include the `--notes` option in their invocation of git-format-patch. Teach git-format-patch the `format.notes` config

Re: [PATCH 2/2] archive: avoid spawning `gzip`

Am 27.04.19 um 11:59 schrieb René Scharfe:> Am 26.04.19 um 16:51 schrieb Johannes Schindelin: >> >> On Mon, 15 Apr 2019, Jeff King wrote: >> >>> On Sun, Apr 14, 2019 at 12:01:10AM +0200, René Scharfe wrote: >>> Doing compression in its own thread may be a good idea. >>> >>> Yeah. It might eve

hi

Hello My Dear Friend, I am Mrs Alysia Macedo I was born 1960 a widow suffering from long time cancer illness. I am contacting you for a transfer of fund inheritance, the sum of ($2,500,000.00 USD). I will forward to you all the information you will use to get this fund released and transferred fr

Re: [PATCH v4 06/10] trace2: use system/global config for default trace2 settings

On Mon, Apr 15, 2019 at 01:39:47PM -0700, Jeff Hostetler via GitGitGadget wrote: > From: Jeff Hostetler > > Teach git to read the system and global config files for > default Trace2 settings. This allows system-wide Trace2 settings to > be installed and inherited to make it easier to manage a co

Re: [PATCH v3 4/8] commit-graph: don't early exit(1) on e.g. "git status"

On Mon, Mar 25 2019, Ævar Arnfjörð Bjarmason wrote: > Make the commit-graph loading code work as a library that returns an > error code instead of calling exit(1) when the commit-graph is > corrupt. This means that e.g. "status" will now report commit-graph > corruption as an "error: [...]" at t

Re: [PATCH v2 0/5] Create commit-graph file format v2

On Fri, Apr 26 2019, Ævar Arnfjörð Bjarmason wrote: > ...speaking of which, digging up outstanding stuff I have on the > commit-graph I was reminded to finish up my "commit graph on clone" > patch in: > https://public-inbox.org/git/87in2hgzin@evledraar.gmail.com/ > > And re #1 above: I guess

READ

-- I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

[PATCH v2 3/3] revisions.txt: mention ~ form

In revisions.txt, the '^' form is mentioned but the '~' form is missing. Although both forms are essentially equivalent (they each get the first parent of the specified revision), we should mention the latter for completeness. Make this change. Signed-off-by: Denton Liu --- Documentation/revisio

[PATCH v2 0/3] cleanup revisions.txt

Thanks for the review, Andreas. I mulled over it for a bit and I think that marking optional arguments with [] would increase the clarity of the documentation so I went ahead and made this change across the whole file. While I was at it, I found some instances of "" written as "rev" so I fixed th

[PATCH v2 2/3] revisions.txt: mark optional rev arguments with []

In revisions.txt, an optional rev argument was not distinguised. Instead, a user had to continue and read the description in order to learn that the argument was optional. Since the [] notation for an optional argument is common-knowledge in the Git documentation, mark optional arguments with [] s

[PATCH v2 1/3] revisions.txt: change "rev" to ""

In revisions.txt, there were some instances of a rev argument being written as "rev". However, since they didn't mean the string literal, write "", instead. Signed-off-by: Denton Liu --- Documentation/revisions.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Docum

[PATCH v3 2/2] branch: make create_branch accept a merge base rev

When we ran something like $ git checkout -b test master... it would fail with the message fatal: Not a valid object name: 'master...'. This was caused by the call to `create_branch` where `start_name` is expected to be a valid rev. However, git-checkout allows the branch to be a valid

[PATCH v3 1/2] t2018: cleanup in current test

Before, in t2018, if do_checkout failed to create `branch2`, the next test-case would run `git branch -D branch2` but then fail because it was expecting `branch2` to exist, even though it doesn't. As a result, an early failure could cause a cascading failure of tests. Make test-case responsible fo

[PATCH v3 0/2] allow checkout and branch to create branches on a merge base

Thanks again for the review, Junio. I've squashed 2/3 and 3/3 together and made that documentation change I was talking about earlier. --- Changes since v2: * Squashed 2/3 with 3/3 * Document merge base syntax for in git-checkout.txt Changes since v1: * Moved multiple `test_when_finished` ca

Re: [PATCH 2/2] archive: avoid spawning `gzip`

Am 26.04.19 um 16:51 schrieb Johannes Schindelin:> Hi Peff, > > On Mon, 15 Apr 2019, Jeff King wrote: > >> On Sun, Apr 14, 2019 at 12:01:10AM +0200, René Scharfe wrote: >> > As we already link to the zlib library, we can perform the compression > without even requiring gzip on the host mach