Re: refs/notes/amlog problems, was Re: [PATCH v3 01/20] linear-assignment: a function to solve least-cost assignment problems

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

 



Hi,

On Fri, 20 Jul 2018, Stefan Beller wrote:

> +cc list
> On Fri, Jul 20, 2018 at 2:29 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > ... which means that it does not matter if I have an elaborate rewrite hook
> > that constantly updates the reverse mapping or if the reverse mapping is
> > made immediately before I push out. You wouldn't even be able to tell any
> > difference.
> >
> > And for that matter, it could even be made on the receiving end by you
> > after you fetch from me before you need the reverse map information.

I refuse to believe that the suggestion to go back to the equivalent of
pencil and paper is sincere. We are developing a state of the art source
code management tool here, not some hodge podge project of somebody who is
trying to teach themselves C.

The current state is that there is no reliable "paper trail" of code
contributions. The solution to that is absolutely not to abolish what
little of a paper trail we *do* have. The solution is to step up the game
and correct that automated record.

And I would have expected a lot better from the inventor of the pickaxe
options: why care so much about source code "archeology" on the one hand,
and then burning the library on the other hand? It just does not make
sense.

Ciao,
Dscho



[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