git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charvi Mendiratta <charvi077@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>,
	Christian Couder <christian.couder@gmail.com>,
	Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: What's cooking in git.git (Jan 2021, #06; Sat, 30)
Date: Mon, 1 Feb 2021 21:21:03 +0530	[thread overview]
Message-ID: <CAPSFM5fLcSBmcGTLaPuoKKHO0qv3fKB5q-XvXv5emWfLYpFv=w@mail.gmail.com> (raw)
In-Reply-To: <xmqqsg6infev.fsf@gitster.c.googlers.com>

On Sun, 31 Jan 2021 at 05:38, Junio C Hamano <gitster@pobox.com> wrote:

> * cm/rebase-i (2021-01-29) 9 commits
>  - doc/git-rebase: add documentation for fixup [-C|-c] options
>  - rebase -i: teach --autosquash to work with amend!
>  - t3437: test script for fixup [-C|-c] options in interactive rebase
>  - rebase -i: add fixup [-C | -c] command
>  - sequencer: use const variable for commit message comments
>  - sequencer: pass todo_item to do_pick_commit()
>  - rebase -i: comment out squash!/fixup! subjects from squash message
>  - sequencer: factor out code to append squash message
>  - rebase -i: only write fixup-message when it's needed
>
>  "rebase -i" is getting cleaned up and also enhanced.
>
>  It seems to break t3415 when merged to 'seen'.
>

I fetched and built the 'seen' branch with merged patches[1]. After that
build all the tests, but at my branch all tests are passing.

Also, I looked at here :
https://github.com/git/git/runs/1803017766

It seems that a lot of tests are failing in macOS. Also in the link t3415 test
is shown passing.
As I have tested on linux/Ubuntu. So, I am unable to get how to figure out
why the tests are failing. Or maybe I am missing something ?

Thanks and Regards,
Charvi

[1] https://lore.kernel.org/git/20210129182050.26143-1-charvi077@gmail.com/

  parent reply	other threads:[~2021-02-01 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  0:00 What's cooking in git.git (Jan 2021, #06; Sat, 30) Junio C Hamano
2021-01-31  1:42 ` Taylor Blau
2021-01-31 20:50   ` Junio C Hamano
2021-01-31 17:21 ` SZEDER Gábor
2021-01-31 20:52   ` Junio C Hamano
2021-01-31 20:11 ` Derrick Stolee
2021-01-31 20:53   ` Junio C Hamano
2021-02-01  0:27 ` Ævar Arnfjörð Bjarmason
2021-02-01  1:48   ` Junio C Hamano
2021-02-02 15:54     ` Johannes Schindelin
2021-02-02 20:18       ` Junio C Hamano
2021-02-01 15:51 ` Charvi Mendiratta [this message]
2021-02-01 19:48   ` Junio C Hamano
2021-02-02 15:28     ` Charvi Mendiratta
2021-02-03  1:08 ` Đoàn Trần Công Danh
2021-02-03  1:22   ` Junio C Hamano
2021-02-03 22:00     ` Miriam R.
2021-02-04  1:38       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPSFM5fLcSBmcGTLaPuoKKHO0qv3fKB5q-XvXv5emWfLYpFv=w@mail.gmail.com' \
    --to=charvi077@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood@dunelm.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).