From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: remote-helpers and refs without a value
Date: Sun, 27 Mar 2011 10:24:28 +0200 [thread overview]
Message-ID: <20110327082428.GA4428@glandium.org> (raw)
Hi,
If I understand correctly how remote helpers work, the values that the
helper returns to the list command is then used to update the remote
branches, or FETCH_HEAD, dependint how the fetch happened.
But when the helper returns a '?' value to the list command, I don't see
how things are supposed to be updated. It looks like the helper is
the only one, then, to be able to update the refs. But it also doesn't
have any way to know which refs it needs to update...
Is it a misunderstanding from my part, or is it something that should be
improved in the remote-helpers support?
Mike
next reply other threads:[~2011-03-27 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 8:24 Mike Hommey [this message]
2011-03-28 7:22 ` remote-helpers and refs without a value Tay Ray Chuan
2011-03-28 7:50 ` Mike Hommey
2011-03-30 1:59 ` Tay Ray Chuan
2011-03-30 6:25 ` Mike Hommey
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=20110327082428.GA4428@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
/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).