Re: [PATCH v3] git checkout: create unparented branch by --orphan

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

 



2010/3/21 Junio C Hamano <gitster@xxxxxxxxx>:
The main point of the feature is not the emptyness of the resulting tree
(it is merely one possible outcome), but is the lack of parents in the
resulting commit. So I would recommend against --empty. --root might be a good synonym, though, and we _do_ already use that word for that purpose
in some commands (e.g. "log --root").

On 2010 Mar 21, at 16:15, Erick Mattos wrote:
--root could be a synonym but the reason I haven't chosen it was the
fact that it could mislead people to think the functionality will do
something with/based on the first commit of the actual branch,
subjectively thinking "THE ROOT".

The existing uses of --root are close to, but not identical to this proposed usage. The existing uses all relate to handling the already created root commit(s) of a commit/branch/repository. This proposed usage relates to the yet to be created first commit on the new branch. It is possible to use the "already created" interpretation in this context (create a new branch based on the root commits of the specified commits), but it really does not make much sense. Still, qualifying "root" might help prevent some confusion:

    --new-root
    --fresh-root
    --root-branch?

    --new-history
    --fresh-history
    --fresh-branch

Logically, both --orphan and --root are descriptions of the commit that will _eventually_ be stored under the branch, but not descriptions of the transient state of the branch itself. This state is described in a few error/warning messages as "not yet born" or "unborn" (checkout, pull, fsck). It seems to be an unofficial term though (or maybe just unimportant) since it is not otherwise documented (it is not in the glossary, but it does appear in the release notes a few times). So with some weight of existing terminology behind it:

    --unborn

--no-parent was mentioned elsewhere in the thread, but it suffers from looking like a negation of a potential --parent option. Though much longer, --without- does not suffer this same problem.

    --without-parents
    --without-history
--ahistorically (probably the non-standard prefix is too "native")

    --ex-nihilo        (just kidding?)

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

[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]