git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: git@vger.kernel.org
Subject: Now What?
Date: Wed, 02 Nov 2005 19:30:37 -0600	[thread overview]
Message-ID: <E1EXTw5-00063o-Gt@jdl.com> (raw)


The Other Day, I offered to help write up some parts of
a "Something weird just happened.  Now What?" document.

So, I'm now soliciting suggestions and/or tips that can
be thrown together to form the basis of that document.

I have a few ideas and a rough outline up my sleeve, but
I am curious to know what _you_ think needs to be covered.

I think one of the most crucial aspects that needs to be
covered well is the "Merge Failed" problem.  So, for starters,
I'd like to get your suggestions on this particular issue.
I know when I see the dreaded "merge by hand" message I
often sit and stare, pondering "Now what?"

I feel that an explanation of all of the behind-the-scripts-
in-.git communication files is needed.  In particular these:

    FETCH_HEAD
    MERGE_HEAD
    LAST_MERGE
    MERGE_MSG

These need to be mentioned and explained because they
frequently form exactly the critical missing link or
starting point after a failed fetch or merge.

Finally, a procedure or style question.  Should this
write-up be in the form of a structured FAQ?  A stand-alone
expository document?

Thanks,
jdl

             reply	other threads:[~2005-11-03  1:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  1:30 Jon Loeliger [this message]
2005-11-03  1:43 ` Now What? Chris Shoemaker
2005-11-03  9:00   ` Junio C Hamano
2005-11-03 18:51   ` Jon Loeliger
2005-11-06 20:33     ` Junio C Hamano
2005-11-03  8:38 ` Peter Eriksen
2005-11-03 10:00   ` Junio C Hamano
2005-11-03 17:05     ` Daniel Barkalow
2005-11-03 17:27       ` Linus Torvalds
2005-11-03 18:38         ` Junio C Hamano
2005-11-03 17:30       ` Peter Eriksen
2005-11-03 22:07       ` Junio C Hamano
2005-11-03 22:33         ` Josef Weidendorfer
2005-11-04 17:06         ` Daniel Barkalow
2005-11-03 17:25   ` Linus Torvalds
2005-11-03  8:58 ` Junio C Hamano
2005-11-03 20:55 ` Junio C Hamano
2005-11-03 22:17   ` Josef Weidendorfer
2005-11-03 22:51     ` Junio C Hamano
2005-11-03 23:26       ` Josef Weidendorfer

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=E1EXTw5-00063o-Gt@jdl.com \
    --to=jdl@freescale.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.
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 NNTP newsgroup(s).