git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: Derrick Stolee <stolee@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] check_everything_connected: assume alternate ref tips are valid
Date: Tue, 2 Jul 2019 01:29:39 -0400	[thread overview]
Message-ID: <20190702052938.GC16344@sigill.intra.peff.net> (raw)
In-Reply-To: <20190701170245.GA54693@TaylorsMBP5815.attlocal.net>

On Mon, Jul 01, 2019 at 12:02:45PM -0500, Taylor Blau wrote:

> One thing that I didn't catch in my initial review that I am seeing now
> is the ".alternate" marker. Why did you choose this? I was thinking that
> ".have" would make more sense since it's consistent with what's shown in
> the ref advertisement, but I think that actually ".alternate" is a
> _better_ choice: the two really do refer to different things.

Yeah, I had called these ".have" originally, but decided that was too
tied up with the current users, and not with the concept. I think
keeping the leading "." is worthwhile as that's an invalid refname.

I also thought about an empty string, but it's probably more informative
to show _something_. After all, the user would not see these unless they
specifically asked for them _and_ used something like --source, so
presumably it's a useful piece of information at that point (I don't
know of any other way to show these names except for --source).

I suppose one other option would be to name them after the oid itself.
So with --source you'd find out that 1234abcd came from 1234abcd (duh),
but also that its children came from 1234abcd. Maybe that has value. I
dunno.

It would be easy to change, but I'd also be OK punting until somebody
comes up with a compelling use case.

-Peff

  reply	other threads:[~2019-07-02  5:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:11 [PATCH] check_everything_connected: assume alternate ref tips are valid Jeff King
2019-06-28 10:18 ` Jeff King
2019-06-28 12:51 ` Derrick Stolee
2019-06-29  7:43   ` Jeff King
2019-07-01 12:25     ` Derrick Stolee
2019-07-01 12:59       ` Jeff King
2019-07-01 13:17         ` Jeff King
2019-07-01 13:17           ` [PATCH 1/2] object-store.h: move for_each_alternate_ref() from transport.h Jeff King
2019-07-01 13:23             ` Derrick Stolee
2019-07-01 13:18           ` [PATCH v2 2/2] check_everything_connected: assume alternate ref tips are valid Jeff King
2019-07-03  9:12             ` SZEDER Gábor
2019-07-03 16:41               ` Jeff King
2019-07-03 16:46                 ` Junio C Hamano
2019-07-03 16:50                 ` SZEDER Gábor
2019-07-03 17:05                   ` Junio C Hamano
2019-07-01 17:02           ` [PATCH] " Taylor Blau
2019-07-02  5:29             ` Jeff King [this message]
2019-06-28 16:22 ` Junio C Hamano
2019-06-29  7:55   ` Jeff King
2019-07-01 12:26     ` Derrick Stolee

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=20190702052938.GC16344@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=stolee@gmail.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;
as well as URLs for NNTP newsgroup(s).