From: Sebastian Schuberth <sschuberth@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git-contacts questions
Date: Tue, 29 Oct 2013 16:02:29 +0100 [thread overview]
Message-ID: <CAHGBnuOT1ttzSuzCt4GDxJ7iap6VM1Sbyuve2FGR7pdf2z40bg@mail.gmail.com> (raw)
In-Reply-To: <vpqsivkywdx.fsf@anie.imag.fr>
On Tue, Oct 29, 2013 at 3:39 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
>> I'm not sure what you're trying to point me at. It's clear that from
>> an implementation view you need to blame HEAD^ if you need to know
>> which poeple should review your changes in HEAD.
>
> I agree that the situation when providing only HEAD is really
> disappointing...
>
>> But IMHO that is an implementation detail that should be hidden from
>> the user.
>
> ... but it's not just an implementation detail: git-contacts takes a
> range of commits, so you can ask for people to Cc for a whole patch
> series for example.
>
> If I understand correctly, "git contact $ONE_COMMIT" does
> "git contact $ONE_COMMIT..HEAD" implicitly, and this is weird when
> $ONE_COMMIT is HEAD.
It's not only weird if $ONE_COMMIT is HEAD, but for any single commit.
At least I would expect "git contacts $ONE_COMMIT" to list the poeple
interested in the single commit $ONE_COMMIT. Instead, what it seems to
do is list the people who are interested in the commits *after*
$ONE_COMMIT.
--
Sebastian Schuberth
next prev parent reply other threads:[~2013-10-29 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 8:34 git-contacts questions Sebastian Schuberth
2013-10-29 8:57 ` Felipe Contreras
2013-10-29 9:12 ` Sebastian Schuberth
2013-10-29 10:35 ` Felipe Contreras
2013-10-29 14:17 ` Sebastian Schuberth
2013-10-29 14:39 ` Matthieu Moy
2013-10-29 15:02 ` Sebastian Schuberth [this message]
2013-10-29 16:59 ` Felipe Contreras
2013-10-29 19:02 ` Eric Sunshine
2013-10-29 20:42 ` Sebastian Schuberth
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=CAHGBnuOT1ttzSuzCt4GDxJ7iap6VM1Sbyuve2FGR7pdf2z40bg@mail.gmail.com \
--to=sschuberth@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).