From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: rms@gnu.org
Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: git is screwed
Date: Thu, 26 Mar 2015 12:11:41 +0100 [thread overview]
Message-ID: <5513E96D.8070204@math.ntnu.no> (raw)
In-Reply-To: <E1Yb5Qq-0006tC-HH@fencepost.gnu.org>
Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > I think it might be useful if you posted the result of running “git
> > status -s” so we can assess the damage.
>
> Here it is. I can only guess what the flags mean,
You can run “git help status” and read what it says under the heading
“Short Format”.
> but if 'M' means it
> is modified on this machine, I am very surprised -- I never touched
> most of those files.
The vast majority have M in the first column and a space in the second.
That means they are modified in the index (uh, staging area is the
modern name for it). They will be the result of the incomplete merge:
Most of them are files that have been modified in the remote repository
but not locally. The Ds have been deleted, and the As have been added.
> M .gitattributes
> M CONTRIBUTE
> […]
The only file with a non-blank second column is here:
> MM lisp/ChangeLog
That's your merge conflict.
I have to go now, no time for the next couple hours. But perhaps someone
else will give you advice.
Perhaps it is useful if you also run these commands and report the output:
git show-ref HEAD
git show-ref master
The latter assuming you're on the master branch. Otherwise, replace
“master” by emacs-24 or whatever branch you're on.
– Harald
next prev parent reply other threads:[~2015-03-26 11:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 14:17 git is screwed Richard Stallman
2015-03-22 14:53 ` Andreas Schwab
2015-03-23 3:25 ` Richard Stallman
[not found] ` <20150322154147.GA6808@Tron.local>
[not found] ` <E1YZszx-0004Ff-JK@fencepost.gnu.org>
2015-03-23 4:52 ` Sam Gwydir
2015-03-23 9:56 ` Harald Hanche-Olsen
2015-03-24 15:54 ` Richard Stallman
2015-03-24 16:26 ` Harald Hanche-Olsen
2015-03-26 10:54 ` Richard Stallman
2015-03-26 11:11 ` Harald Hanche-Olsen [this message]
2015-03-26 11:27 ` Harald Hanche-Olsen
2015-03-26 12:21 ` Steinar Bang
2015-03-26 14:16 ` Stefan Monnier
2015-03-26 17:04 ` Eli Zaretskii
2015-03-26 19:02 ` Steinar Bang
2015-03-26 20:29 ` Eli Zaretskii
2015-03-26 22:34 ` Stefan Monnier
2015-03-27 7:24 ` Eli Zaretskii
2015-03-27 13:09 ` Stefan Monnier
2015-03-27 19:35 ` Steinar Bang
2015-03-27 19:59 ` Eli Zaretskii
2015-03-27 20:36 ` Steinar Bang
2015-03-27 19:30 ` Steinar Bang
2015-03-26 10:54 ` Richard Stallman
2015-03-26 15:10 ` John Wiegley
2015-03-26 10:54 ` Richard Stallman
2015-03-25 8:29 ` Steinar Bang
2015-03-25 10:29 ` Artur Malabarba
2015-03-25 12:41 ` Stefan Monnier
2015-03-25 13:42 ` Steinar Bang
2015-03-25 14:32 ` Artur Malabarba
2015-03-25 23:23 ` Jonas Bernoulli
2015-03-26 0:35 ` Stefan Monnier
2015-03-26 1:42 ` John Yates
2015-03-26 2:04 ` Stefan Monnier
2015-03-26 8:00 ` Steinar Bang
2015-03-26 8:28 ` Alexis
2015-03-26 8:41 ` Alexis
2015-03-26 8:58 ` Artur Malabarba
2015-03-26 10:27 ` Rasmus
2015-03-26 19:01 ` Ricardo Wurmus
2015-03-26 19:08 ` Rasmus
2015-03-26 23:41 ` Jonas Bernoulli
2015-04-01 20:41 ` Harald Hanche-Olsen
2015-04-03 11:00 ` Richard Stallman
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=5513E96D.8070204@math.ntnu.no \
--to=hanche@math.ntnu.no \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.