From: Erick Mattos <erick.mattos@gmail.com>
To: Peter Baumann <waste.manager@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v3] git checkout: create unparented branch by --orphan
Date: Sun, 21 Mar 2010 14:55:03 -0300 [thread overview]
Message-ID: <55bacdd31003211055r348f37b0sb4ff02c38c64722b@mail.gmail.com> (raw)
In-Reply-To: <20100321171431.GE2557@m62s10.vlinux.de>
Hi,
2010/3/21 Peter Baumann <waste.manager@gmx.de>:
> Sorry to skim in so late but --orphan sounds - at least to me as a non native
> speaker - a little strange. Yes, I know it means "without parents", but
> actually it would be the *last* thing I would search for after opening the
> manpage.
It is never late to contribute, even for skimming. Free software are
organic and living things people can mold it whenever they want.
We are both non native English speakers but for me orphan is the real
obvious for no parents. And that is the name of the command you type:
shorter and not similar to other ones is the best.
I don't care about names as long as its bearer does what it is
supposed to do. But in this particular case I think it fits the job.
> Wouldn't --empty-parent or --no-parent describe the situation better?
> It actually has the benefit that it would match on a search for /parent/,
> which I would have searched for if I want to create a new empty branch.
--empty-parent try to give the "plumbing" idea but it is not really
'empty' but 'non-existant' and also it is not good to make
"porcelainners" (inventing this term) see it as an unparented though.
--no-parent is just added characters and make it feel as if it exists
a --parent too.
You WILL match on a search for /parent/ already.
> --
> Peter
>
Thanks for you contributing ideas.
Although I don't agree with you on this subject, I am very happy you
participated your ideas to me. It is good to get some attention :-)
In this particular case I see Junio as a native English speaker better
fitted to comment.
Best regards
next prev parent reply other threads:[~2010-03-21 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 15:34 [PATCH v3] git checkout: create unparented branch by --orphan Erick Mattos
2010-03-21 17:14 ` Peter Baumann
2010-03-21 17:55 ` Erick Mattos [this message]
2010-03-21 19:37 ` Junio C Hamano
2010-03-21 21:15 ` Erick Mattos
2010-03-22 8:54 ` Michael J Gruber
2010-03-22 12:46 ` Chris Johnsen
2010-03-22 14:36 ` Erick Mattos
2010-03-21 21:38 ` Junio C Hamano
2010-03-22 12:43 ` Chris Johnsen
2010-03-22 14:14 ` Erick Mattos
2010-03-22 16:06 ` Translating error messages in Git (was: Re: [PATCH v3] git checkout: create unparented branch by --orphan) Jakub Narebski
2010-03-22 20:19 ` [PATCH v3] git checkout: create unparented branch by --orphan Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55bacdd31003211055r348f37b0sb4ff02c38c64722b@mail.gmail.com \
--to=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=waste.manager@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).