From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Sylvain Joyeux <sylvain.joyeux@dfki.de>,
Junio C Hamano <gitster@pobox.com>,
Lars Hjemli <hjemli@gmail.com>, Ping Yin <pkufranky@gmail.com>,
Mark Levedahl <mlevedahl@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] better git-submodule status output
Date: Mon, 7 Jul 2008 16:23:02 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807071621300.18205@racer> (raw)
In-Reply-To: <32541b130807070757s4ba03e28tf4701f479e27b687@mail.gmail.com>
Hi,
On Mon, 7 Jul 2008, Avery Pennarun wrote:
> On 7/7/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Mon, 7 Jul 2008, Avery Pennarun wrote:
> > > Thus, I'd say the best fix would be to find a way to have "git pull" or
> > > "git fetch" in the supermodule also do a fetch in the submodule.
> >
> > Noooooo!
> >
> > If I am actively working on the submodule, the supermodule has _no
> > business_ trying to wreck my state.
>
> Hmm... how does doing a fetch wreck your state?
It updates the tracking branches. And guess what I use the tracking
branches for? Yes, to track other people's changes.
It would wreck my state.
Anyway, fetch is wrong, wrong, wrong, if all you want to do is see the
_state_ of your submodule.
If that state is that the superproject has a commit that the submodule
knows nothing about, then that is _exactly_ what needs to be reported.
Don't play cute games,
Dscho
next prev parent reply other threads:[~2008-07-07 15:25 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 [this message]
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
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=alpine.DEB.1.00.0807071621300.18205@racer \
--to=johannes.schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hjemli@gmail.com \
--cc=mlevedahl@gmail.com \
--cc=pkufranky@gmail.com \
--cc=sylvain.joyeux@dfki.de \
/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