From: Jens Lehmann <Jens.Lehmann@web.de>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] fetch: Only call a new ref a "branch" if it's under refs/heads/.
Date: Thu, 12 Apr 2012 22:42:20 +0200 [thread overview]
Message-ID: <4F873E2C.6080808@web.de> (raw)
In-Reply-To: <4F873CD0.4050204@xiplink.com>
Am 12.04.2012 22:36, schrieb Marc Branchaud:
> I assumed it was an optimization of some sort -- that since tags are normally
> only fetched when they're part of a requested branch's history (right?),
> there was no point in doing submodule recursion on the fetched tags since
> those tagged tree-ishes had already been submodule-recursed.
If that is the case the patch I just sent is pointless, but adding a comment
there explaining that would be a good thing ;-)
next prev parent reply other threads:[~2012-04-12 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 14:29 [PATCH] fetch: Only call a new ref a "branch" if it's under refs/heads/ marcnarc
2012-04-12 5:52 ` Jeff King
2012-04-12 20:15 ` Jens Lehmann
2012-04-12 20:36 ` Marc Branchaud
2012-04-12 20:42 ` Jens Lehmann [this message]
2012-04-12 21:05 ` Jeff King
2012-04-13 7:04 ` Jeff King
2012-04-13 16:25 ` [PATCH] submodules: recursive fetch also checks new tags for submodule commits Jens Lehmann
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=4F873E2C.6080808@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.