git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: rajdeep mondal <justrajdeep@gmail.com>
To: Mike Hommey <mh@glandium.org>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>, git@vger.kernel.org
Subject: Re: Feature request: Please add support to stash specific files
Date: Tue, 6 Jun 2017 18:00:36 -0400	[thread overview]
Message-ID: <CACkx65BrZv3bVmYZ1s03GGe-eqfzvgKQbzoLN0WD6by3Zn16og@mail.gmail.com> (raw)
In-Reply-To: <20170606210318.e2ey4pwxhxsuvizi@glandium.org>

Thanks Mike.

On Tue, Jun 6, 2017 at 5:03 PM, Mike Hommey <mh@glandium.org> wrote:
> On Tue, Jun 06, 2017 at 02:38:08PM -0400, rajdeep mondal wrote:
>> Hi Randall,
>>
>> I completely agree to what you are saying, but sometimes it just so
>> happens that in the middle of a change, i feel like if some portion of
>> the changes are fine I can commit them.  Stashing some of the files
>> and being able to check the compile/tests at this point would be a
>> really awesome change.
>>
>> Stash supports a -p option to deal with this, it becomes cumbersome
>> when the number of files are many.  Maybe it is something which would
>> be a good to have feature. People need not use it if they dont want
>> to.
>
> Git 2.13.0 has that already.
>
> git stash -- file1 file2
>
> Mike



-- 
==============================
Rajdeep
==============================

  reply	other threads:[~2017-06-06 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 13:23 Feature request: Please add support to stash specific files rajdeep mondal
2017-06-06 13:31 ` Randall S. Becker
2017-06-06 18:38   ` rajdeep mondal
2017-06-06 21:03     ` Mike Hommey
2017-06-06 22:00       ` rajdeep mondal [this message]
2017-06-06 13:42 ` Christian Neukirchen

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=CACkx65BrZv3bVmYZ1s03GGe-eqfzvgKQbzoLN0WD6by3Zn16og@mail.gmail.com \
    --to=justrajdeep@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=rsbecker@nexbridge.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).