git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git-Bug

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jun 25, 2022, 12:16 UTC
Message-ID
<Yrb8tJDNxEJOuU+4@tapette.crustytoothpaste.net>
In-Reply-To
<YrbHPlJy/EW/Y+ON@ikki.ethgen.ch>
On 2022-06-25 at 08:28:46, Klaus Ethgen wrote:
Show 46 quoted lines
> Hi,
> 
> since some versions I have the following troubles with git:
> 
> I use vcsh to manage my vim config files and pull/push them from one
> machine to others. That was working great but now the push refuses to
> work as it state the working tree is unclean even if it is clean:
> 
>    # on the server:
>    ~> vcsh vim config receive.denyCurrentBranch
>    updateInstead
>    ~> vcsh vim config core.excludesfile
>    .gitignore.d/vim
>    ~> vcsh vim status
>    Auf Branch master
>    Ihr Branch ist auf demselben Stand wie 'origin/master'.
> 
>    nichts zu committen, Arbeitsverzeichnis unverändert
> 
>    # on the client:
>    ~> vcsh vim status
>    Auf Branch master
>    Ihr Branch ist 3 Commits vor 'xxxx/master'.
>      (benutzen Sie "git push", um lokale Commits zu publizieren)
> 
>    nichts zu committen, Arbeitsverzeichnis unverändert
>    ~> vcsh vim push
>    Objekte aufzählen: 10, fertig.
>    Zähle Objekte: 100% (9/9), fertig.
>    Delta-Kompression verwendet bis zu 2 Threads.
>    Komprimiere Objekte: 100% (6/6), fertig.
>    Schreibe Objekte: 100% (6/6), 821 Bytes | 821.00 KiB/s, fertig.
>    Gesamt 6 (Delta 4), Wiederverwendet 0 (Delta 0), Pack wiederverwendet 0
>    To xxxx:.config/vcsh/repo.d/vim.git
>     ! [remote rejected] master -> master (Working directory has unstaged changes)
>    error: Fehler beim Versenden einiger Referenzen nach 'xxxx:.config/vcsh/repo.d/vim.git'
> 
> `vcsh ... command` does the same ad `vcsh ... && git command`... vcsh is
> a simple script that sets GIT_DIR to ~/.config/vcsh/repo.d/....git. vcsh
> is used to manage config files in $HOME but not the full directory. In
> this example, it manages .vimrc, .gvimrc, .vim/ and .exrc.
> 
> As you can see, there is no unstaged changes but git tell me there are.
> 
> I tried different things but failed to tell git that everything is clean
> and that there are no unstaged changes.

Do you have files that would be unstaged after you pushed? Are there ignored files in that directory that would conflict with what you've pushed?

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
Previous: Klaus Ethgen
Message 2 of 2 in “Git-Bug”
  1. Klaus EthgenJun 25, 2022
  2. brian m. carlsonJun 25, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.