git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mehul Jain <mehul.jain2029@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: GSoC 2016: Microproject
Date: Sun, 21 Feb 2016 21:32:37 +0530	[thread overview]
Message-ID: <CA+DCAeSpN+OSJ85yyqq9ONzfubh=coMd7FTct5OkEnLvhMm2tw@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kbdTFui5Zxmt0+BrgOzxTFsN2n-XZiJBNj4QFD3HPRpBQ@mail.gmail.com>

On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller <sbeller@google.com> wrote:
> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right
> place as judging from the file name of the tests.

I checked out both of the files and made following observations -

1) As I'm going to add an option for "git pull --rebase"; tests should
be added for following commands in t/t5521-pull-options.sh
          a)  git pull --rebase --[no-]autostash
          b)  git pull -v --rebase --[no-]autostash
          c)  git pull -q --rebase --[no-]autostash

2) Also test for "pull --rebase --[no-]autostash fails with dirty
working tree and rebase.autostash set" should be added to
t/t5520-pull.sh.

Have I made the right observation?

Thanks,
Mehul Jain

  parent reply	other threads:[~2016-02-21 17:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  8:59 GSoC 2016: Microproject Mehul Jain
2016-02-19 13:03 ` Matthieu Moy
2016-02-19 17:39   ` Mehul Jain
2016-02-19 17:50     ` Stefan Beller
2016-02-19 18:32       ` Mehul Jain
2016-02-20 14:43       ` Mehul Jain
2016-02-21  4:55         ` Matthieu Moy
2016-02-21 16:04           ` Mehul Jain
2016-02-21 18:52             ` Matthieu Moy
2016-02-22  8:10               ` Karthik Nayak
2016-02-22 10:12               ` Mehul Jain
2016-02-22 10:20                 ` Duy Nguyen
2016-02-22 10:30                   ` Mehul Jain
2016-02-22 11:21                     ` Duy Nguyen
2016-02-22 12:28                       ` Mehul Jain
2016-02-22 10:21                 ` Lars Schneider
2016-02-22 10:30                   ` Lars Schneider
2016-02-21 16:02       ` Mehul Jain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-27 13:04 GSoC 2016 Microproject Sidhant Sharma
2016-02-27 13:28 ` Matthieu Moy
2016-02-27 15:20   ` Sidhant Sharma
2016-02-27 16:12     ` Matthieu Moy
2016-02-28 10:12       ` Sidhant Sharma
2016-02-29 14:51         ` Sidhant Sharma
2016-02-29 15:04         ` Matthieu Moy
2016-02-29 15:32           ` Sidhant Sharma
2016-02-29 15:51             ` Matthieu Moy
2016-03-01 11:38               ` Sidhant Sharma
2016-03-01 12:22                 ` Thomas Gummerer

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='CA+DCAeSpN+OSJ85yyqq9ONzfubh=coMd7FTct5OkEnLvhMm2tw@mail.gmail.com' \
    --to=mehul.jain2029@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.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).