git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Birger Skogeng Pedersen <birger.sp@gmail.com>
To: git@vger.kernel.org
Subject: BUG: On some Linux systems, "Stage To Commit" hotkey in git-gui stages one file only, even if multiple files are selected
Date: Wed, 7 Feb 2018 14:29:09 +0100	[thread overview]
Message-ID: <CAGr--=+V6zBo_0c_pX=PNVq1+8N-Q14+wgYx1j_odSGcRAv0hQ@mail.gmail.com> (raw)

In git-gui, multiple files from the "Unstaged Changes" widget can be
selected. Once multiple files are selected, they can be staged by
clicking (toolbar) "Commit"->"Stage To Commit". All the files that
were selected then gets staged for the commit. The "Stage To Commit"
hotkey (CTRL+T) behaves like the command itself, staging all files
that are selected (Tested on Windows 10).
However, on some linux systems (currently tested on Ubuntu 17.10),
only one file (the most recently selected) gets staged when using the
"Stage To Commit" hotkey (CTRL+T), while the other, selected files
remain unstaged.

Steps to reproduce (on Ubuntu 17.10):
- Open git-gui in a repository with two or more unstaged, changed files
- Select two or more files in the "Unstaged Changes"
- Click CTRL+T to stage the files that you have selected
(Only a single file will get staged)

             reply	other threads:[~2018-02-07 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 13:29 Birger Skogeng Pedersen [this message]
2018-02-07 18:11 ` BUG: On some Linux systems, "Stage To Commit" hotkey in git-gui stages one file only, even if multiple files are selected Eric Sunshine

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='CAGr--=+V6zBo_0c_pX=PNVq1+8N-Q14+wgYx1j_odSGcRAv0hQ@mail.gmail.com' \
    --to=birger.sp@gmail.com \
    --cc=git@vger.kernel.org \
    /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).