All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Joyeux <sylvain.joyeux@dfki.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] better git-submodule status output
Date: Wed, 9 Jul 2008 15:46:29 +0200	[thread overview]
Message-ID: <20080709134629.GA3848@joyeux> (raw)
In-Reply-To: <alpine.DEB.1.00.0807091427270.5277@eeepc-johanness>

> >   On the symbols side, I propose:
> >     > submodule commit is a direct descendant of the commit in the
> >       superproject
> >     < submodule commit is a direct ancestor of the commit in the
> >       superproject
> >     + no direct relation between submodule commit and commit in the
> >       superproject
> >     ? the commit in the superproject cannot be found in the submodule
> >       (replaces the initial '!' in my patch)
> 
> I like the output of "git checkout" when your local branch is not agreeing 
> with the tracked branch.  Maybe it would be more user-friendly to have 
> submodule use that type of message, instead of cryptic single letter?
Mmmm ... Yes that could be a great idea. I'll try it.
 
> On a related note, the long commit name has been a constant nuisance for 
> me.  A short commit name is perfectly enough, methinks.
I also think so. The commit ID is completely useless for humans.
Nonetheless, that would change the git-submodules output which
(according to someone-that-I-dont-remember) would be a Bad Thing(tm).

> > - define a git-submodule 'fetch' subcommand which call fetch in each
> >   submodule and runs the verbose mode of git-status (can be disabled by
> >   a --quiet option).
> 
> I like it.
> 
> You probably can refactor the code for "update" to do that nicely.
OK

Sylvain

  reply	other threads:[~2008-07-09 13:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 15:01 [PATCH] better git-submodule status output Sylvain Joyeux
2008-07-06  6:19 ` Junio C Hamano
2008-07-06 12:57   ` Johannes Schindelin
2008-07-06 16:07     ` Sylvain Joyeux
2008-07-06 16:29       ` Johannes Schindelin
2008-07-07  6:21         ` Sylvain Joyeux
2008-07-07 14:25           ` Avery Pennarun
2008-07-07 14:34             ` Johannes Schindelin
2008-07-07 14:37               ` Johannes Schindelin
2008-07-07 14:57                 ` Sylvain Joyeux
2008-07-07 15:21                   ` Johannes Schindelin
2008-07-07 15:42                     ` Sylvain Joyeux
2008-07-07 18:20                   ` Junio C Hamano
2008-07-07 18:29                     ` Avery Pennarun
2008-07-07 19:51                       ` Junio C Hamano
2008-07-08  8:00                     ` Sylvain Joyeux
2008-07-08 11:21                       ` Johannes Schindelin
2008-07-08 12:22                         ` Sylvain Joyeux
2008-07-08 13:00                           ` Johannes Schindelin
2008-07-08 13:12                             ` Sylvain Joyeux
2008-07-07 14:57               ` Avery Pennarun
2008-07-07 15:23                 ` Johannes Schindelin
2008-07-07 15:36                   ` Avery Pennarun
2008-07-07 16:10                     ` Johannes Schindelin
2008-07-07 15:52                   ` Sylvain Joyeux
2008-07-07 15:00             ` Sylvain Joyeux
2008-07-06 13:14   ` Mark Levedahl
2008-07-09 10:13 ` Sylvain Joyeux
2008-07-09 10:25   ` Andreas Ericsson
2008-07-09 11:01     ` Sylvain Joyeux
2008-07-09 12:31   ` Johannes Schindelin
2008-07-09 13:46     ` Sylvain Joyeux [this message]
2008-07-09 13:54       ` Johannes Schindelin
2008-07-09 18:48   ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-07-01 14:57 Sylvain Joyeux

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=20080709134629.GA3848@joyeux \
    --to=sylvain.joyeux@dfki.de \
    --cc=Johannes.Schindelin@gmx.de \
    --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.