Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always
From: Stefan Beller <sbeller@xxxxxxxxxx>
Date: Mon, 30 Jul 2018 10:06:25 -0700
Cc: Derrick Stolee <dstolee@xxxxxxxxxxxxx>, git <git@xxxxxxxxxxxxxxx>
In-reply-to: <86y3ds6b40.fsf@gmail.com>
References: <pull.11.git.gitgitgadget@gmail.com> <20180718152244.45513-1-dstolee@microsoft.com> <86y3ds6b40.fsf@gmail.com>

> I wonder though if all those changes to the testsuite shouldn't be
> merged.

I think Stolee doesn't want this to be merged after rereading
subject and the commit message.

Thanks,
Stefan

Follow-Ups:
- Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always
  - From: Jakub Narebski

References:
- [PATCH 0/8] Clarify commit-graph and grafts/replace/shallow incompatibilities
  - From: Derrick Stolee via GitGitGadget
- [PATCH] DO-NOT-MERGE: write and read commit-graph always
  - From: Derrick Stolee
- Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always
  - From: Jakub Narebski

Prev by Date: Re: [PATCH v4 11/21] range-diff: add tests
Next by Date: Re: [PATCH/RFC] Color merge conflicts
Previous by thread: Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always
Next by thread: Re: [PATCH] DO-NOT-MERGE: write and read commit-graph always
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux