Re: [PATCH 1/2] commit-graph write: add progress output

On Wed, Sep 05 2018, Derrick Stolee wrote: > On 9/4/2018 6:07 PM, Junio C Hamano wrote: >> Ævar Arnfjörð Bjarmason writes: >> >>> With --stdin-packs we don't show any estimation of how much is left to >>> do. This is because we might be processing more than one pack. We >>> could be less lazy

Re: [PATCH 0/2] commit-graph: add progress output

On 9/4/2018 4:27 PM, Ævar Arnfjörð Bjarmason wrote: This series adds progress output to the commit-graph command, so that when it's called by "git gc" or "git fsck" we can see what's going on with it. Ævar Arnfjörð Bjarmason (2): commit-graph write: add progress output commit-graph verify:

Re: [PATCH 1/2] commit-graph write: add progress output

On 9/4/2018 4:27 PM, Ævar Arnfjörð Bjarmason wrote: @@ -591,8 +597,13 @@ static void close_reachable(struct packed_oid_list *oids) { int i; struct commit *commit; + struct progress *progress = NULL; + int j = 0; The change below over-counts the number of commits we

Re: [PATCH 1/2] commit-graph write: add progress output

On 9/4/2018 6:07 PM, Junio C Hamano wrote: Ævar Arnfjörð Bjarmason writes: With --stdin-packs we don't show any estimation of how much is left to do. This is because we might be processing more than one pack. We could be less lazy here and show progress, either detect by detecting that we're

Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)

On Wed, Sep 05 2018, Eric Sunshine wrote: > On Wed, Sep 5, 2018 at 4:29 AM Ævar Arnfjörð Bjarmason > wrote: >> I recently gained access to a Solaris 10 SPARC (5.10) box and discovered >> that the chainlint.sed implementation in 2.19.0 has more sed portability >> issues. >> >> First, whoever im

Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)

On Tue, Sep 4, 2018 at 6:36 PM Junio C Hamano wrote: > * es/worktree-forced-ops-fix (2018-08-30) 9 commits > - worktree: delete .git/worktrees if empty after 'remove' > - worktree: teach 'remove' to override lock when --force given twice > - worktree: teach 'move' to override lock when --force

Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)

On Tue, Sep 4, 2018 at 6:36 PM Junio C Hamano wrote: > * es/worktree-forced-ops-fix (2018-08-30) 9 commits > - worktree: delete .git/worktrees if empty after 'remove' > - worktree: teach 'remove' to override lock when --force given twice > - worktree: teach 'move' to override lock when --force

Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)

On Wed, Sep 5, 2018 at 4:29 AM Ævar Arnfjörð Bjarmason wrote: > I recently gained access to a Solaris 10 SPARC (5.10) box and discovered > that the chainlint.sed implementation in 2.19.0 has more sed portability > issues. > > First, whoever implemented the /bin/sed on Solaris apparently read the >

[RFC PATCH v2] Allow aliases that include other aliases

Aliases can only contain non-alias git commands and their arguments, not other user-defined aliases. Resolving further (nested) aliases is prevented by breaking the loop after the first alias was processed. Git then fails with a command-not-found error. Allow resolving nested aliases by not breaki

Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)

On Tue, Sep 04 2018, Junio C Hamano wrote: > Git 2.19-rc2 is out. Hopefully the tip of 'master' is more or less > identical to the final one without needing much updates. > > You can find the changes described here in the integration branches > of the repositories listed at > > http://git-b

Re: Git in Outreachy Dec-Mar?

On Mon, Sep 3, 2018 at 6:36 AM, Christian Couder wrote: > On Sat, Sep 1, 2018 at 10:43 AM, Jeff King wrote: >> On Fri, Aug 31, 2018 at 10:16:49AM +0200, Christian Couder wrote: >> >>> > 2. To get our landing page and list of projects in order (and also >>> > micro-projects for applicants).

<    1   2