git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Git List <git@vger.kernel.org>, Marc Branchaud <marcnarc@xiplink.com>
Subject: Re: [PATCH] submodule: use abbreviated sha1 in 'status' output
Date: Mon, 1 Oct 2012 12:12:30 +0530	[thread overview]
Message-ID: <CALkWK0mqkWvveA6NX36R0L5tQE_wnRwyFu0LncLY6ORXRK-KYA@mail.gmail.com> (raw)
In-Reply-To: <50670E39.8080101@web.de>

Jens Lehmann wrote:
> I suspect you got the idea for this patch from Marc's recent comment:
> [...]

Yes, I did.

> That is just a single user so far indicating your patch /could/ be an
> improvement. I think we need quite some more votes on that before we
> should do a change like this.

I thought it's a porcelain command like 'git status'- we don't need
votes to change the output format of 'git status', do we?

Ram

  reply	other threads:[~2012-10-01  6:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 13:43 [PATCH] submodule: make 'show' an alias for 'summary' Ramkumar Ramachandra
2012-09-29 13:43 ` [PATCH] submodule: use abbreviated sha1 in 'status' output Ramkumar Ramachandra
2012-09-29 14:31   ` Jens Lehmann
2012-09-29 14:45     ` Ramkumar Ramachandra
2012-09-29 15:05       ` Jens Lehmann
2012-10-01  6:42         ` Ramkumar Ramachandra [this message]
2012-10-01 17:22           ` Jens Lehmann
2012-09-29 14:49 ` [PATCH] submodule: make 'show' an alias for 'summary' Jens Lehmann
2012-09-29 15:07   ` Ramkumar Ramachandra
2012-09-29 15:27     ` Jens Lehmann
2012-10-01  6:45       ` Ramkumar Ramachandra
2012-10-01 17:26         ` Jens Lehmann
2012-10-01 17:33           ` Ramkumar Ramachandra
2012-10-01 19:31             ` Jens Lehmann
2012-10-01 17:41           ` Junio C Hamano

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=CALkWK0mqkWvveA6NX36R0L5tQE_wnRwyFu0LncLY6ORXRK-KYA@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=marcnarc@xiplink.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).