git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Joyeux <sylvain.joyeux@dfki.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: 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: Sun, 6 Jul 2008 18:07:59 +0200	[thread overview]
Message-ID: <20080706160758.GA23385@jhaampe.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0807061456100.3486@wbgn129.biozentrum.uni-wuerzburg.de>

> > Which one is the commit message ;-)?
> 
> I think it is clear that Sylvain has not read 
> Documentation/SubmittingPatches yet.

Sylvain *has* read SubmittingPatches but has not understood every detail of this
very long document.

If you could enlighten me on what is wrong ...

> > People who rely on working submodule support, do you have any feedback 
> > on this patch?
> 
> Not yet.  Will test/comment when the spurious "fetch" is fixed.
I thought that the only thing that 'fetch' does is update FETCH_HEAD. My problem
is that doing the fetch is the only way to know what is the status of the
submodule w.r.t. the registered commit. If you have a better way to get that
information, I'm all ears :P

--
Sylvain

  reply	other threads:[~2008-07-06 16:37 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 [this message]
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
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=20080706160758.GA23385@jhaampe.org \
    --to=sylvain.joyeux@dfki.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hjemli@gmail.com \
    --cc=mlevedahl@gmail.com \
    --cc=pkufranky@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.
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).