Re: Antw: Re: non-smooth progress indication for git fsck and git gc

>>> Jeff King schrieb am 21.08.2018 um 03:07 in Nachricht <20180821010712.ga32...@sigill.intra.peff.net>: > On Mon, Aug 20, 2018 at 10:57:13AM +0200, Ævar Arnfjörð Bjarmason wrote: > [...] > So it really should just be a simple: > > progress = start_delayed_progress("Hashing packfile", 0); >

Re: Antw: Re: non-smooth progress indication for git fsck and git gc

cht <87woslpg9i@evledraar.gmail.com>: > On Mon, Aug 20 2018, Ulrich Windl wrote: > >>>>> Jeff King schrieb am 16.08.2018 um 22:55 in Nachricht >> <20180816205556.ga8...@sigill.intra.peff.net>: >>> On Thu, Aug 16, 2018 at 10:35:53PM +0200, Ævar Ar

Antw: Re: non-smooth progress indication for git fsck and git gc

>>> Jeff King schrieb am 16.08.2018 um 22:55 in Nachricht <20180816205556.ga8...@sigill.intra.peff.net>: > On Thu, Aug 16, 2018 at 10:35:53PM +0200, Ævar Arnfjörð Bjarmason wrote: > >> This is all interesting, but I think unrelated to what Ulrich is talking >> about. Quote: >> >> Between

Antw: Re: non-smooth progress indication for git fsck and git gc

>>> Duy Nguyen schrieb am 16.08.2018 um 17:18 in Nachricht : > On Thu, Aug 16, 2018 at 1:10 PM Ulrich Windl > wrote: >> >> Hi! >> >> I'd like to point out some minor issue observed while processing some > 5-object repository with many binary objects

non-smooth progress indication for git fsck and git gc

Hi! I'd like to point out some minor issue observed while processing some 5-object repository with many binary objects, but most are rather small: Between the two phases of "git fsck" (checking directories and checking objects) there was a break of several seconds where no progress was

Antw: Re: Q: Ignore ./foo, but not script/foo

tually, when read carefully enough, the last item in "PATTERN FORMAT" explains that. Maybe the EXAMPLES could have an example for each item (5 cases) described ;-) Regards, Ulrich > > Best regards, > Sebastian > Am Do., 19. Juli 2018 um 09:45 Uhr schrieb Ulrich Windl >

Q: Ignore ./foo, but not script/foo

Hi! I have a (simple) question I could not answer elegantly from the gitignore(5) manual page: A project produces a "foo" binary in the root directory that I want to ignore (So I put "foo" into .gitignore) Unfortunately I found out taht I cannot have a "script/foo" added while "foo" is in

Antw: Re: java diffs show no method context

> schrieb am 25.04.2018 um 17:05 in Nachricht <aae8d748-101d-1eb2-f8e8-9da2e53e2...@gmail.com>: > Le 25/04/2018 à 14:53, Ulrich Windl a écrit : >> Hi! >> >> This is for git 2.13.6, and it may be an FAQ or frequent feature request. > Anyway: >> I'm new to Java,

java diffs show no method context

Hi! This is for git 2.13.6, and it may be an FAQ or frequent feature request. Anyway: I'm new to Java, and writing my first project using Git, I found that "git diff" only reports the class in the diff context, but not the method (as seen for C, for example). I'd wish to have the method where

Antw: Re: Re: bug deleting "unmerged" branch (2.12.3)

; with manual pages referring to it. Regards, Ulrich >>> "Philip Oakley" <philipoak...@iee.org> schrieb am 08.12.2017 um 21:26 in Nachricht <582105F8768F4DA6AF4EC82888F0BFBE@PhilipOakley>: > From: "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de>

Antw: Re: bug deleting "unmerged" branch (2.12.3)

Hi Philip! I'm unsure what you are asking for... Ulrich >>> "Philip Oakley" 04.12.17 0.30 Uhr >>> From: "Junio C Hamano" > "Philip Oakley" writes: > >> I think it was that currently you are on M, and neither A nor B are >>

Antw: Re: bug deleting "unmerged" branch (2.12.3)

> "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> writes: > >> I think if more than one branches are pointing to the same commit, >> one should be allowed to delete all but the last one without >> warning. Do you agree? > > That comes from a view

Antw: Re: bug deleting "unmerged" branch (2.12.3)

> Hi Ulrich, > > On Tue, 28 Nov 2017, Ulrich Windl wrote: > >> During a rebase that turned out to be heavier than expected 8-( I >> decided to keep the old branch by creating a temporary branch name to >> the commit of the branch to rebase (which was still the

bug deleting "unmerged" branch (2.12.3)

Hi! During a rebase that turned out to be heavier than expected 8-( I decided to keep the old branch by creating a temporary branch name to the commit of the branch to rebase (which was still the old commit ID at that time). When done rebasing, I attached a new name to the new (rebased) branch,

Problems in Default merge message

Hi! I'd like to report an old-time bug in git, regarding the default message visible for a "git merge --no-commit" (at the later commit, of course): * When merging a branch, the first name is put in single quotes, while the second is not. * There is no blank line after the first one * there

Antw: Re: Terrible bad performance for it blame --date=iso -C -C master --

>>> Samuel Lijin schrieb am 03.05.2017 um 09:12 in Nachricht

Antw: Re: Terrible bad performance for it blame --date=iso -C

>>> Jakub Narebski <jna...@gmail.com> schrieb am 03.04.2017 um 17:16 in Nachricht <0ccc5cab-26b7-4b02-b964-452b61e92...@gmail.com>: > W dniu 03.04.2017 o 12:56, SZEDER Gábor pisze: >> Ulrich Windl wrote: > >>> In the other case (for the user bored of

Antw: Re: Terrible bad performance for it blame --date=iso -C -C master --

be how to avoid that. Regards, Ulrich >>> Junio C Hamano <gits...@pobox.com> schrieb am 31.03.2017 um 17:52 in >>> Nachricht <xmqq60ip1m0f....@gitster.mtv.corp.google.com>: > "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> writes: > >> I was run

Terrible bad performance for it blame --date=iso -C -C master --

Hi! I was running "vc-annotate" in Emacs for a file from a large repository (>4 files, a big percentage being binary, about 10 commits). For the first file the result was presented rather soon, but for a second file the command did not finish even after about 10 minutes! The file in

Antw: Re: Enhancement Request: locale git option

Ralf Thielow ralf.thie...@gmail.com schrieb am 04.12.2014 um 20:02 in Nachricht CAN0XMOL5ZZgEJ3zaXOAcxyX47iTM-DQv=+pnsdvrjd4awwx...@mail.gmail.com: Hi Ulrich, 2014-12-04 8:32 GMT+01:00 Ulrich Windl ulrich.wi...@rz.uni-regensburg.de: Hi! I'm native German, but German git messages confuse me

Antw: Re: Enhancement Request: locale git option

Ralf Thielow ralf.thie...@gmail.com schrieb am 06.12.2014 um 20:28 in Nachricht CAN0XMO+hn0cYrd=gvpuad_mqcvknwdfzfln0vo7045-m_0g...@mail.gmail.com: 2014-12-05 16:45 GMT+01:00 Torsten Bögershausen tbo...@web.de: I do not know who was first, and who came later, but

Antw: Re: Enhancement Request: locale git option

Torsten Bögershausen tbo...@web.de schrieb am 04.12.2014 um 09:29 in Nachricht 54801b50.4080...@web.de: On 12/04/2014 08:32 AM, Ulrich Windl wrote: Hi! I'm native German, but German git messages confuse me (yopu'll have to correlate them with the man pages). At the moment git uses

Enhancement Request: locale git option

Hi! I'm native German, but German git messages confuse me (yopu'll have to correlate them with the man pages). At the moment git uses the locale settings from the environment, so you can only change git's locale settings by changing the environment (like LANG= git ...). OTOH Git has a flexible

Antw: Re: Extended splitting for git add --interactive

@gitster.dls.corp.google.com: Ulrich Windl ulrich.wi...@rz.uni-regensburg.de writes: This is for git-1.7.12 (an older version from the SLES11 SP3 SDK). If the issue is solved meanwhile, I'll be happy, and I apologize for being too lazy to find out. The answer is no ;-). Currently Git cannot split a block

Extended splitting for git add --interactive

belonging to one of AAA or BBB, or into three parts where the empty line is just another junk to accept or refuse. See comment above on why I'd like that. Regards, Ulrich Windl -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More

Antw: Re: Q: .git/HEAD and .git/refs/heads

Matthieu Moy matthieu@grenoble-inp.fr schrieb am 02.04.2014 um 19:54 in Nachricht vpqob0jwrbb@anie.imag.fr: Ulrich Windl ulrich.wi...@rz.uni-regensburg.de writes: Hi! I have a small question: After a git gc with last commit being [shared 2679648] I found this: cat .git/HEAD

Q: .git/HEAD and .git/refs/heads

/info/refs Of course I'd be most pleased if there was some git builtin to get that (I read the manual without success). Using an older version of Git (git-1.7.12)... Regards, Ulrich Windl -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord

Antw: Re: diff support for the Eiffel language?

, Ulrich Johannes Sixt j.s...@viscovery.net schrieb am 22.10.2012 um 15:35 in Nachricht 50854b90.50...@viscovery.net: Am 10/22/2012 15:06, schrieb Ævar Arnfjörð Bjarmason: On Mon, Oct 22, 2012 at 1:58 PM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: However there's one little thing I

diff support for the Eiffel language?

Hi! After a longer pause, I did some programming in Eiffel again, and while doing so, why not use Git? It works! However there's one little thing I noticed with git diff: The conte4xt lines (staring with @@) show the current function (in Perl and C), but they show the current feature clause in