git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/4] rev-parse: deprecate use as an option sifter
Date: Fri, 14 May 2010 21:01:15 +0200	[thread overview]
Message-ID: <201005142101.16317.jnareb@gmail.com> (raw)
In-Reply-To: <4BED9C09.8010801@drmicha.warpmail.net>

Dnia piątek 14. maja 2010 20:52, Michael J Gruber napisał:
> Jakub Narebski venit, vidit, dixit 14.05.2010 17:41:
> > Michael J Gruber <git@drmicha.warpmail.net> writes:
> > 
> >>  NAME
> >>  ----
> >> -git-rev-parse - Pick out and massage parameters
> >> +git-rev-parse - Parse symbolic names into object names
> > 
> > What about "git rev-parse --parseopt"?  Isn't it massaging parameters?
> > 
> 
> Sure it is. But if you read the part of the patch that you cut out (i.e.
> the comment and relevant diff) you see that the massaging part is the
> deprecated part of it. That's why I suggest not mentioning it at the
> most prominent place. (I don't suggest removing that functionality.)

"git rev-parse --parseopt" is not deprecated.  What is deprecated is
--revs-only, --flags, etc.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2010-05-14 19:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01 18:36 [RFD PATCH] revlist/rev-parse: Introduce --heads and --locals revision specifiers Michael J Gruber
2010-05-01 19:42 ` Jakub Narebski
2010-05-01 19:47   ` Michael J Gruber
2010-05-01 19:51     ` Jakub Narebski
2010-05-02  5:00 ` Jeff King
2010-05-02 13:43   ` Michael J Gruber
2010-05-05  3:35     ` Jeff King
2010-05-13 14:24       ` [PATCH 0/4] All is too much Michael J Gruber
2010-05-13 14:24         ` [PATCH 1/4] rev-parse: deprecate use as an option sifter Michael J Gruber
2010-05-14 15:41           ` Jakub Narebski
2010-05-14 18:52             ` Michael J Gruber
2010-05-14 19:01               ` Jakub Narebski [this message]
2010-05-14 19:22                 ` Michael J Gruber
2010-05-17 14:26                 ` Thomas Rast
2010-05-13 14:24         ` [PATCH 2/4] t6018: add tests for rev-list's --branches and --tags Michael J Gruber
2010-05-13 14:24         ` [PATCH 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-13 14:24         ` [PATCH 4/4] revlist: Introduce --lrbranches and --locals revision specifiers Michael J Gruber
2010-05-14  6:06         ` [PATCH 0/4] All is too much Jeff King
2010-05-14 16:08           ` Michael J Gruber
2010-05-14 16:14             ` Git methodology question Akhbari, Farshad
2010-05-14 21:44               ` Chris Packham
2010-05-14 21:54               ` Avery Pennarun
2010-05-14 18:26             ` [PATCH v2 0/4] All is too much Michael J Gruber
2010-05-14 18:26               ` [PATCH v2 1/4] rev-parse: deprecate use as an option sifter Michael J Gruber
2010-05-14 18:26               ` [PATCH v2 2/4] t6018: add tests for rev-list's --branches and --tags Michael J Gruber
2010-05-14 18:26               ` [PATCH v2 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-14 18:26               ` [PATCH v2 4/4] revlist: Introduce --lrbranches and --locals revision specifiers Michael J Gruber

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=201005142101.16317.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).