From: Finn Arne Gangstad <finnag@pvv.org>
To: Klas Lindberg <klas.lindberg@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Users List <git@vger.kernel.org>
Subject: Re: Fetching SHA id's instead of named references?
Date: Mon, 6 Apr 2009 15:16:43 +0200 [thread overview]
Message-ID: <20090406131643.GA16229@pvv.org> (raw)
In-Reply-To: <33f4f4d70904060606h4d014fbdibe195a83233d8899@mail.gmail.com>
On Mon, Apr 06, 2009 at 03:06:46PM +0200, Klas Lindberg wrote:
> On Mon, Apr 6, 2009 at 2:54 PM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
>
> > What Johannes pointed out is that someone could fetch from your repo
> > _after_ you correct the mistake (if you don't control garbage
> > collection).
>
> Aha, ok. But how then does submodule update work? Git will only see
> SHA keys for each submodule in the cotntainer tree commit, so how does
> it perform fetching of those (unnamed) references?
git submodule update just does "git fetch" and hopes that the required
commit appears. In practice this means that you (may) need to invent a
tag or a branch for all the submodules, otherwise they are not
fetchable.
This bit us pretty hard when we tried to use submodules earlier, so we
gave up. Maybe some day...
- Finn Arne
next prev parent reply other threads:[~2009-04-06 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 12:13 Fetching SHA id's instead of named references? Klas Lindberg
2009-04-06 12:33 ` Johannes Schindelin
2009-04-06 12:41 ` Klas Lindberg
2009-04-06 12:48 ` Johannes Schindelin
2009-04-06 21:50 ` Dmitry Potapov
2009-04-06 12:54 ` Matthieu Moy
2009-04-06 13:06 ` Klas Lindberg
2009-04-06 13:16 ` Finn Arne Gangstad [this message]
2009-04-06 14:40 ` Shawn O. Pearce
2009-04-06 16:22 ` Klas Lindberg
2009-04-06 16:55 ` Nicolas Pitre
2009-04-06 23:40 ` Klas Lindberg
2009-04-07 2:34 ` Nicolas Pitre
2009-04-08 20:03 ` Klas Lindberg
2009-04-08 20:38 ` Nicolas Pitre
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090406131643.GA16229@pvv.org \
--to=finnag@pvv.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=klas.lindberg@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).