All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Palczewski <l.palczewski@prevac.pl>
To: git@vger.kernel.org
Subject: Re: Restart submodule update --recursive
Date: Fri, 29 Oct 2010 07:17:03 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101029T085153-262@post.gmane.org> (raw)
In-Reply-To: 20101028181515.GB14212@burratino

Hi Jonathan,

Jonathan Nieder writes:

> [...]
> But if there are many, many submodules, it could be better to script
> a --save-progress and --resume along the lines you described.
> 
> Two possible approaches:
> 
>  - Make a new script using "git submodule foreach --recursive" that
>    steps through the list by hand, or
> 
>  - Take cmd_update from git-submodule.sh in the git sources and modify
>    to taste.
> [...]

I think modyfying the git-submodule.sh will be better for me. So I looked into
it and first problem araised: 
How do I get a name of submodule with a name of a previous submodule?
Maybe I will start with how my repository looks like:

Main
 |
 --> sub1
 |     |
 |     --> nsub1
 |     |
 |     --> nsub2
 |     |
 |     --> nsub3
 |     |
 |     --> etc.     
 |
 --> sub2
 |     |
 |     --> nsub2 (no nsub1)
 |     |
 |     --> nsub3
 |     |
 |     --> nsub4
 |
 --> sub3
 |     |
 |     --> nsub1
 |     |
 |     --> nsub3 (no nsub2)
 |     |
 |     --> nsub4
 |
 etc.

It would be nice if I could get name like this sub1/nsub1 when I am in submodule
sub1. Right now, I can get submodule name: nsub1. I tried to find some commands
to get something like this, but could not find it.

If I can get that, I will be in home. Do You know how to do it?
BTW. thanks for previous suggestion.

Lukasz Palczewski

  reply	other threads:[~2010-10-29  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28  7:25 Restart submodule update --recursive Lukasz Palczewski
2010-10-28 10:35 ` Johan Herland
2010-10-29  7:28   ` Lukasz Palczewski
2010-10-28 18:15 ` Jonathan Nieder
2010-10-29  7:17   ` Lukasz Palczewski [this message]
2010-10-29  9:12     ` Jonathan Nieder
2010-10-29 11:37       ` Lukasz Palczewski
2010-10-29 16:40         ` Jonathan Nieder
2010-10-30  7:17         ` Jens Lehmann
2010-11-02  8:18           ` Lukasz Palczewski
2010-11-02 11:08             ` 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=loom.20101029T085153-262@post.gmane.org \
    --to=l.palczewski@prevac.pl \
    --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 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.