unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Łukasz Stelmach" <l.stelmach@samsung.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 26309@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#26309: 24.4; vc-git-register doesn't run interactively
Date: Thu, 30 Mar 2017 16:30:48 +0200	[thread overview]
Message-ID: <87o9wi4z1j.fsf%l.stelmach@samsung.com> (raw)
In-Reply-To: <mvmy3vmlubj.fsf@suse.de>

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

It was <2017-03-30 czw 16:20>, when Andreas Schwab wrote:
> On Mär 30 2017, Łukasz Stelmach <l.stelmach@samsung.com> wrote:
>> It was <2017-03-30 czw 15:51>, when Noam Postavsky wrote:
>>> On Thu, Mar 30, 2017 at 9:05 AM, Łukasz Stelmach <l.stelmach@samsung.com> wrote:
>>>
>>>> The vc-git-register function can't be used, neither bound to a key
>>>> shortcut nor via M-x, to quickly add current file to index.
>>>
>>> Doesn't C-x v i (or M-x vc-register) work?
>>
>> Not really. It works for a file that hasn't been added to a repo
>> yet. But once I add it, make some changes and want to add the modified
>> version I get:
>>
>>     vc-register: This file is already registered
>
> VC doesn't use the git index, so there is no need to update it.

Does it mean that before commiting (with vc) all files "git status"
shows as modified would be added to index automatically?

Anyway, I like to "git add" files I am working with from time to time. 
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  parent reply	other threads:[~2017-03-30 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170330130513eucas1p2ca60345aff5282dd8916971bee36bf1d@eucas1p2.samsung.com>
2017-03-30 13:05 ` bug#26309: 24.4; vc-git-register doesn't run interactively Łukasz Stelmach
2017-03-30 13:51   ` Noam Postavsky
     [not found]     ` <CGME20170330140455eucas1p1cd577c5a6a38095e7085f70c869ca064@eucas1p1.samsung.com>
2017-03-30 14:04       ` Łukasz Stelmach
2017-03-30 14:20         ` Andreas Schwab
     [not found]           ` <CGME20170330143109eucas1p2bbb6175dcc95b0d29ee1f4275466110c@eucas1p2.samsung.com>
2017-03-30 14:30             ` Łukasz Stelmach [this message]
2017-03-30 14:50               ` Noam Postavsky
     [not found]                 ` <CGME20170330150948eucas1p191eac45190f0a0afec1a8ffbbc36b9e7@eucas1p1.samsung.com>
2017-03-30 15:09                   ` Łukasz Stelmach
2017-03-30 16:31                     ` Dmitry Gutov
2017-03-31 12:12                       ` Thien-Thi Nguyen
2019-09-29 14:50                       ` Lars Ingebrigtsen
2017-03-30 18:43   ` bug#26309: [PATCH] (vc-git-register): register current file when called interactively Łukasz Stelmach

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o9wi4z1j.fsf%l.stelmach@samsung.com \
    --to=l.stelmach@samsung.com \
    --cc=26309@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=schwab@suse.de \
    /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://git.savannah.gnu.org/cgit/emacs.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).