Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)

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

Subject: Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
From: Johannes Sixt <j6t@xxxxxxxx>
Date: Wed, 6 Dec 2017 19:34:26 +0100
Cc: git@xxxxxxxxxxxxxxx, Nikolay Shustov <nikolay.shustov@xxxxxxxxx>, Johannes Schneider <mailings@xxxxxxxxxxxxx>, Patrik Gornicz <patrik-git@xxxxxxxxxxxxxxxxx>, Martin Waitz <tali@xxxxxxxxxxxxxx>, Shawn Pearce <spearce@xxxxxxxxxxx>, Sam Vilain <sam@xxxxxxxxxx>, Jakub Narebski <jnareb@xxxxxxxxx>
In-reply-to: <7ae3ffd5-147d-55d2-9630-da12c429d631@gmail.com>
References: <8998e832-f49f-4de4-eb8d-a7934fba97b5@gmail.com> <d5f243a5-6e35-f3fc-4daf-6e1376bef897@kdbg.org> <203a75c8-0c58-253c-2c18-05450f7ae49b@gmail.com> <ea156b8b-29d8-7501-b5a5-a29cfbd7d1d6@kdbg.org> <741dfedc-07f8-24fb-ebe2-940f8b2639d4@gmail.com> <33e97533-716b-e1cc-6aa0-bf8941225319@kdbg.org> <7ae3ffd5-147d-55d2-9630-da12c429d631@gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

I am sorry for not responding in detail. I think we've reached a mutualunderstanding of our workflows.

Though, from the ideas you tossed around most recently, you seem to wantto make git-commit into a kitchen-sink for everything. I have my doubtsthat this will be a welcome change. Just because new commits are createddoes not mean that the feature must live in git-commit.


-- Hannes

Follow-Ups:
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Junio C Hamano

References:
- [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Igor Djordjevic
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Johannes Sixt
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Igor Djordjevic
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Johannes Sixt
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Igor Djordjevic
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Johannes Sixt
- Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
  - From: Igor Djordjevic

Prev by Date: Re: [PATCH v4 1/4] Makefile: generate Perl header from template file
Next by Date: Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
Previous by thread: Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
Next by thread: Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)
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]