git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: skimo@liacs.nl
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: repo.or.cz wishes?
Date: Thu, 30 Aug 2007 01:12:51 +0200	[thread overview]
Message-ID: <200708300112.51666.jnareb@gmail.com> (raw)
In-Reply-To: <20070829073212.GQ1976MdfPADPa@greensroom.kotnet.org>

On Wed, Aug 29, 2007, Sven Verdoolaege wrote:
> On Tue, Aug 28, 2007 at 11:56:10PM +0200, Jakub Narebski wrote:
>> On Tue, 28 August 2007, Sven Verdoolaege wrote:
>>> On Mon, Aug 27, 2007 at 11:58:42PM +0200, Jakub Narebski wrote:
>>>>
>>>> The problem is that repo.or.cz needs support for that in gitweb, while
>>>> gitweb in turn needs support for that in git. This needs git consensus
>>>> on how to specify object database location (or just gitdir) for
>>>> submodules, to have later submodule support in gitweb.
>>> 
>>> What would be the use of that (outside of gitweb) ?
>> 
>> For the hypothetical (planned?) future '--recurse-submodules' option
>> to git-diff family, git-ls-tree and git-ls-files, git-fetch and git-push
>> (but I think not git-pull), perhaps git-log (besides what it supports
>> by the way of git-diff-tree), maybe even git-status and git-commit.
> 
> Ah... you're talking about bare repositories, right?
> For non-bare repos, I'd assume you would only recurse for those
> submodules that you have actually checked out in your working tree.

For bare repositories, and for repositories which move around (at least
once change path). Gitweb uses repository like it is bare...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2007-08-29 23:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 23:59 repo.or.cz wishes? Petr Baudis
2007-08-27  0:16 ` Sven Verdoolaege
2007-08-27  0:41   ` Petr Baudis
2007-08-27 18:23     ` Linus Torvalds
2007-08-27 18:58       ` Junio C Hamano
2007-08-27 19:09       ` Matthieu Moy
2007-08-27 20:05       ` Martin Mares
2007-08-27 21:27         ` Jing Xue
2007-08-27 22:27         ` Linus Torvalds
2007-08-27 22:58           ` Sam Vilain
2007-08-27 23:17             ` Linus Torvalds
2007-08-27 23:27               ` Jakub Narebski
2007-08-27 23:38                 ` Linus Torvalds
2007-08-27 23:30               ` Sam Vilain
2007-08-27 23:34                 ` Linus Torvalds
2007-08-27 23:16           ` Jakub Narebski
2007-08-27 21:58     ` Jakub Narebski
     [not found]       ` <20070828084939.GF1976MdfPADPa@greensroom.kotnet.org>
     [not found]         ` <200708282356.10605.jnareb@gmail.com>
2007-08-29  7:32           ` Sven Verdoolaege
2007-08-29 23:12             ` Jakub Narebski [this message]
2007-08-27  2:40 ` Sam Vilain
2007-08-27  8:35 ` Johannes Schindelin
     [not found]   ` <20070828041059.GK18160@spearce.org>
     [not found]     ` <20070828111913.GA31120@thunk.org>
     [not found]       ` <Pine.LNX.4.64.0708281230310.28586@racer.site>
     [not found]         ` <20070829042005.GT18160@spearce.org>
2007-08-29  9:54           ` Petr Baudis
     [not found]       ` <20070829041523.GS18160@spearce.org>
     [not found]         ` <7vr6lnszay.fsf@gitster.siamese.dyndns.org>
2007-08-29  9:58           ` Petr Baudis
2007-08-29 11:13         ` Theodore Tso
2007-08-31 21:09           ` Shawn O. Pearce
2007-08-29 17:11         ` Linus Torvalds
2007-09-01  2:58           ` Shawn O. Pearce
2007-08-27 19:49 ` Uwe Kleine-König

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=200708300112.51666.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=skimo@liacs.nl \
    /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).