git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSOC proposal

From
Fredrik Gustafsson <iveqy@iveqy.com>
Date
Mar 25, 2011, 10:06 UTC
Message-ID
<20110325100600.GA30376@paksenarrion.iveqy.com>
In-Reply-To
<7vtyes6pya.fsf@alter.siamese.dyndns.org>
On Thu, Mar 24, 2011 at 04:47:41PM -0700, Junio C Hamano wrote:
Show 19 quoted lines
> Jens Lehmann <Jens.Lehmann@web.de> writes:
> 
> >> == Preventing false "pointers" ==
> >> It's far too easy to push a gitrepo pointing to a submodule version that
> >> is not existing on the server. Prevent this by checking for available
> >> submodule versions before acceptingt the push.
> >
> > Yes, requiring to force such a push is an issue raised quite often (I
> > think addressing this issue would be a good starting point for people
> > who want to get involved in enhancing the submodule experience).
> 
> You need to be careful, though.
> 
> That check can only be sanely done at a hosting site that hosts _both_ the
> superproject and the submodule repositories.  It might make more sense to
> have this check on the side that pushes, which by definition should have
> both superprojet and the submodule.  Fail, or prompt to confirm, a push
> from the superproject when it is detected that the submodule commits bound
> to the commits in the superproject have not been pushed out.
I can see three different ways of doing this:
1. the reciever (server) checks for available submodules before
accepting a commit
2. the sender checks for available submodules on the server before
sending a commit.
3. each submodule contains a flag that tells if the last command was a
commit or a push. The core-repository wont allow a push if one (or more)
submodules has a commit as "last command".

Although alternative 1 is the only one that is certain of preventing the problem with "false pointers", it has several other drawbacks. I believe that alt. 3 is the proper way of handling this in git. Although we doesn't guarantee a sane server-repo we does prevent the client from doing stupid things by mistake.

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com
Previous: Junio C HamanoNext: Jens Lehmann
Message 4 of 6 in “GSOC proposal”
  1. Fredrik GustafssonMar 24, 2011
  2. Jens LehmannMar 24, 2011
  3. Junio C HamanoMar 24, 2011
  4. Fredrik GustafssonMar 25, 2011
  5. Jens LehmannMar 25, 2011
  6. Fredrik GustafssonMar 25, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.