git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Jens.Lehmann@web.de, sschuberth@gmail.com
Cc: git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Subject: [RFC_PATCHv4 0/7] Git submodule labels
Date: Mon, 21 Mar 2016 19:06:05 -0700	[thread overview]
Message-ID: <1458612372-10966-1-git-send-email-sbeller@google.com> (raw)

This series introduces labels which you can attach to submodules like so:

    $ cat .gitmodules
    [submodule "gcc"]
        path = gcc
        url = git://...
        label = default
        label = devel
    [submodule "linux"]
        path = linux
        url = git://...
        label = default
        
    $ git submodule add --name emacs --label "editor" --label default git://...
    
    # If upstream has submodules properly labeled, you can make use of them:
    $ git config --add submodule.actionOnLabel "*default"
    $ git config --add submodule.actionOnLabel ":name"
    $ git config --add submodule.actionOnLabel "./by/path"
    # The prefix * denotes a label as found in .gitmodules
    # : goes before names 
    # path are prefixed ./ currently
    # both path and names need work

    # no --init necessary, partially initializes submodules (only those which
    # were specified by label, name or path)
    $ git submodule update
    
    # time passes, upstream may have added new submodules and we get them without
    # extra commands!
    $ git submodule update

    # The above configuration can be given to git clone directly via:
    $ git clone --init-submodule=*labelA ...
    
    # diff/status only apply to label-selected submodules
    git status

New since last round:
* Renamed to submodule.actionOnLabel as it is generic enough to be applicable
  for lots of commands (submodule update, status, diff, etc)
* Restructured the code to have a generic "Given these labels, would I
  want to operate on this submodule", which made the implementation for
  "submodule update" easier, as well as the new WIP patch for diff/status.

Any feedback would be welcome!
Thanks,
Stefan

An earlier version was posted at
http://thread.gmane.org/gmane.comp.version-control.git/284612

This applies on top of origin/sb/submodule-init or can be found at
https://github.com/stefanbeller/git/tree/submodule-groups-v4

Stefan Beller (7):
  git submodule: teach `add` to label submodules
  submodule-config: keep labels around
  submodule-config: add method to check for being labeled
  submodule init: redirect stdout to stderr
  submodule update: respect submodule.actionOnLabel
  clone: allow specification of submodules to be cloned
  WIP status/diff: respect submodule.actionOnLabel

 Documentation/git-clone.txt     |   6 +
 Documentation/git-submodule.txt |   5 +-
 builtin/clone.c                 |  40 +++++-
 builtin/submodule--helper.c     |  25 +++-
 git-submodule.sh                |  14 +-
 submodule-config.c              |  66 ++++++++-
 submodule-config.h              |   5 +
 submodule.c                     |  15 ++
 t/t7400-submodule-basic.sh      | 294 ++++++++++++++++++++++++++++++++++++++++
 9 files changed, 462 insertions(+), 8 deletions(-)

-- 
2.7.0.rc0.45.g6b4c145

             reply	other threads:[~2016-03-22  2:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22  2:06 Stefan Beller [this message]
2016-03-22  2:06 ` [RFC_PATCHv4 1/7] git submodule: teach `add` to label submodules Stefan Beller
2016-03-22 22:28   ` Junio C Hamano
2016-03-22 22:34   ` Junio C Hamano
2016-03-22  2:06 ` [RFC_PATCHv4 2/7] submodule-config: keep labels around Stefan Beller
2016-03-22  2:06 ` [RFC_PATCHv4 3/7] submodule-config: add method to check for being labeled Stefan Beller
2016-03-22 22:30   ` Junio C Hamano
2016-03-23 21:05     ` Stefan Beller
2016-03-22  2:06 ` [RFC_PATCHv4 4/7] submodule init: redirect stdout to stderr Stefan Beller
2016-03-22  7:46   ` Sebastian Schuberth
2016-03-22 16:14     ` Junio C Hamano
2016-03-22 16:47       ` Stefan Beller
2016-03-22 16:56         ` Sebastian Schuberth
2016-03-22 17:15       ` Junio C Hamano
2016-03-22  2:06 ` [RFC_PATCHv4 5/7] submodule update: respect submodule.actionOnLabel Stefan Beller
2016-03-22 22:40   ` Junio C Hamano
2016-03-23 23:21     ` Stefan Beller
2016-03-24  0:13       ` Junio C Hamano
2016-03-24 19:54         ` Stefan Beller
2016-03-24 21:14           ` Junio C Hamano
2016-03-22  2:06 ` [RFC_PATCHv4 6/7] clone: allow specification of submodules to be cloned Stefan Beller
2016-03-22  2:06 ` [RFC_PATCHv4 7/7] WIP status/diff: respect submodule.actionOnLabel Stefan Beller

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=1458612372-10966-1-git-send-email-sbeller@google.com \
    --to=sbeller@google.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=sschuberth@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).