CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Show outdated diffs on github
Date: Fri, 16 Aug 2013 10:00:29 +0200	[thread overview]
Message-ID: <520DDC1D.5010406@dachary.org> (raw)
In-Reply-To: <520DCE40.90505@inktank.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

Thanks for the tip !

On 16/08/2013 09:01, Josh Durgin wrote:
> On 08/15/2013 11:45 PM, Loic Dachary wrote:
>> Hi Josh,
>>
>>  From https://github.com/ceph/ceph/pull/504 I see that your comments persisted despite a rebase and show as
>>
>>   jdurgin discussed an outdated diff 8 hours ago
>>
>> I would like to do the same but when I comment inline, it shows differently and gets trashed by a rebase. I'm curious to learn how you do it :-)
> 
> The interface isn't ideal - if you comment on the pull request diff
> (i.e. https://github.com/ceph/ceph/pull/504/files) instead of the
> individual commits, then your comments will stay associated with the
> pull request (and still appear on new versions of the branch if the
> line they're on didn't change).
> 
> Josh

-- 
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

      reply	other threads:[~2013-08-16  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  6:45 Show outdated diffs on github Loic Dachary
2013-08-16  7:01 ` Josh Durgin
2013-08-16  8:00   ` Loic Dachary [this message]

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=520DDC1D.5010406@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.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