git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rhodes, Kate" <masukomi@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: git-who
Date: Wed, 8 Oct 2008 09:48:12 -0400	[thread overview]
Message-ID: <8323B5AF-AECC-4576-BA85-382BAD8FE74B@gmail.com> (raw)
In-Reply-To: <48EC4F9D.4020202@viscovery.net>


No. No, that's far too simple.


;)

-Kate

On Oct 8, 2008, at 2:13 AM, Johannes Sixt wrote:
> Rhodes, Kate schrieb:
>> Once upon a someone asked about seeing who had touched some files.  
>> Petr
>> Baudis responded with a quickie script that did the job.
>
> Wouldn't
>
>   git shortlog -s -- path/to/file
>
> solve your problem?
>
> -- Hannes
>

  reply	other threads:[~2008-10-08 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 21:02 git-who Rhodes, Kate
2008-10-07 22:35 ` git-who Miklos Vajna
2008-10-08  2:25 ` git-who Jeff King
2008-10-08  4:59   ` git-who Rhodes, Kate
2008-10-08  6:13 ` git-who Johannes Sixt
2008-10-08 13:48   ` Rhodes, Kate [this message]
2008-10-08 18:35   ` git-who Linus Torvalds

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=8323B5AF-AECC-4576-BA85-382BAD8FE74B@gmail.com \
    --to=masukomi@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /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).