From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Olivier Marin <dkr+ml.git@free.fr>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] remote show: fix the -n option
Date: Mon, 9 Jun 2008 03:35:28 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806090330490.1783@racer> (raw)
In-Reply-To: <484C901B.6000401@free.fr>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1479 bytes --]
Hi,
On Mon, 9 Jun 2008, Olivier Marin wrote:
> Johannes Schindelin a écrit :
>
> >> struct option options[] = {
> >> OPT_GROUP("show specific options"),
> >> - OPT__DRY_RUN(&dry_run),
> >> + OPT_BOOLEAN('n', NULL, &no_query, "do not query remotes"),
> >
> > Why?
>
> Because I think it's something different. It's more like in "route -n"
> than --dry-run in "patch --dry-run". Don't you think ?
No, I think that the information about stale branches and if the branches
are up-to-date is missing. In that sense, it is not like "route -n" at
all, which just skips one convenience step, but really a dry run, because
the result is different (as opposed to differently displayed).
> >> + transport = transport_get(NULL, states.remote->url_nr > 0 ?
> >
> > Please rewrap.
>
> I'm not sure what you are talking about. Should I wrap after "NULL,"
> instead of "?"?
It is a too long line (way over 80 characters). So yes, you should wrap
after the NULL here.
> > Maybe we need two different values of got_states; not calling
> > ls-remote and then showing things is okay, but calling ls-remote,
> > getting an error and _then_ showing stuff is not okay, IMO.
>
> In fact, it seems that get_ref_states() always return 0 or just die when
> an error occur. And that transport_get_remote_refs() never return if
> something goes wrong.
>
> So, what about removing got_states and use !no_query instead ?
Hrmpf. I did not mean to die() there...
Ciao,
Dscho
next prev parent reply other threads:[~2008-06-09 2:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 0:54 remote show/prune: strange -n(--dry-run) option Olivier Marin
2008-06-08 11:03 ` [PATCH] Documentation/git-remote.txt: remove description for useless -n option Olivier Marin
2008-06-08 12:22 ` dkr+ml.git
2008-06-08 20:27 ` Junio C Hamano
2008-06-09 0:43 ` Olivier Marin
2008-06-09 0:48 ` [PATCH] remote show: fix the " Olivier Marin
2008-06-09 1:16 ` Johannes Schindelin
2008-06-09 2:06 ` Olivier Marin
2008-06-09 2:35 ` Johannes Schindelin [this message]
2008-06-09 4:16 ` Olivier Marin
2008-06-09 4:53 ` Johannes Schindelin
2008-06-09 14:22 ` Olivier Marin
2008-06-09 15:43 ` Olivier Marin
2008-06-09 16:31 ` Johannes Schindelin
2008-06-09 15:58 ` [PATCH v2] " Olivier Marin
2008-06-09 16:35 ` Johannes Schindelin
2008-06-09 16:58 ` Olivier Marin
2008-06-09 17:56 ` Johannes Schindelin
2008-06-09 18:37 ` Olivier Marin
2008-06-09 20:11 ` [PATCH] builtin-remote: make reuse of code easier by not die()ing Johannes Schindelin
2008-06-09 20:43 ` Olivier Marin
2008-06-10 1:10 ` [PATCH v2] remote show: fix the -n option Junio C Hamano
2008-06-10 1:19 ` Shawn O. Pearce
2008-06-10 2:39 ` Johannes Schindelin
2008-06-10 14:50 ` [PATCH 0/4] remote show/prune improvement Olivier Marin
2008-06-10 14:51 ` [PATCH 1/4] remote show: fix the -n option Olivier Marin
2008-06-10 14:51 ` [PATCH 2/4] builtin-remote: split show_or_prune() in two separate functions Olivier Marin
2008-06-10 14:51 ` [PATCH 3/4] remote prune: print the list of pruned branches Olivier Marin
2008-06-12 7:00 ` Junio C Hamano
2008-06-12 11:07 ` Olivier Marin
2008-06-10 14:51 ` [PATCH 4/4] remote show: list tracked remote branches with -n Olivier Marin
2008-06-10 19:12 ` Junio C Hamano
2008-06-10 22:54 ` [PATCH v2 " Olivier Marin
2008-06-10 15:09 ` [PATCH 0/4] remote show/prune improvement Jakub Narebski
2008-06-10 16:10 ` Olivier Marin
2008-06-10 17:11 ` Jakub Narebski
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=alpine.DEB.1.00.0806090330490.1783@racer \
--to=johannes.schindelin@gmx.de \
--cc=dkr+ml.git@free.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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