Re: [PATCH v6 00/14] Serialized Git Commit Graph

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 16, 2018, 11:50 UTC
Message-ID: <nycvar.QRO.7.76.6.1803161249060.56@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
In-Reply-To: <xmqq37115ggs.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Thu, 15 Mar 2018, Junio C Hamano wrote:

Show 12 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > Stolee, you definitely want to inspect those changes (`git log --check`
> > was introduced to show you whitespace problems). If all of those
> > whitespace issues are unintentional, you can fix them using `git rebase
> > --whitespace=fix` in the most efficient way.
> 
> Another way that may be easier (depending on the way Derrick works)
> is to fetch from me and start working from there, as if they were
> the last set of commits that were sent to the list.  "git log
> --first-parent --oneline master..pu" would show where the tip of the
> topic is.

That is not really easier. We had that discussion before. Stolee would have to remove your Signed-off-by: lines *manually*.

I understand that it is a trade-off between time you have to spend and that others have to spend, and since you do not scale, that trade-off has to be in your favor.

My hope is that we will eventually collaborate more effectively using Git itself, then those trade-offs will become a lot less involved because the overall cost will be a lot smaller.

Ciao, Dscho