Re: Upcoming sparse release RC5

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

 



On Mon, Aug 7, 2017 at 7:38 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote:
>
> You need to make "for-chris" fast forwardable from master.

Chris, that makes no sense at all.

If you ever apply any other patches than the patches from Luc,
suddenly his "for-chris" is no longer fast-forwardeable.

Why do you want that stupid linear history in the first place? Why
can't you just merge Luc's git tree? That's how git is supposed to
work, and it makes it easier for everybody.

This whole rebasing is a disease. It is basically *impossible* to work
sanely with other people if you keep rebasing.

You mustn't rebase other peoples work (because that causes tons of
extra work for them) when you pull, and if you apply any other patches
(or commit any of your own work), then Luc's branch by definition will
need merging.

Nobody else works like you do. Yes, other people have unstable
branches (eg git's own "pu" branch), but those are for experimental
stuff, not for working with anybody else.

Rebasing really is wrong for any pubic tree. Its' fine for your own
_private_ pacthes, as you develop and clean up a branch that you're
still working on, but it shouldn't be an integration model.

                   Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux