unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19049@debbugs.gnu.org
Subject: bug#19049: 25.0.50; emacs-repository-get-version doesn't work with git
Date: Fri, 14 Nov 2014 16:16:57 +0100	[thread overview]
Message-ID: <m3389lstg6.fsf@stories.gnus.org> (raw)
In-Reply-To: <837fyxizql.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Nov 2014 17:11:14 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> No, that's just the beginning.  Almost every question asked about this
> resulted in umpteen different answers.  Which one(s) to choose is
> another obstacle to negotiate, and it's not always easy, because each
> alternative has its subtle pro's and con's.
>
> We had 10 months and enough git expertise to discuss this and decide
> what's best.  And we wasted it.

Well, I think the problem here is that git experts really aren't the
people who are best suited to explain these things.  They don't know
what the incomprehensible things are.  "Well, of course you have to
stash the refs in the staging area!  That's self-evident!  You can't
merge if you have unstaged refs that point to the foreign origin!  I
mean master!"

So we get these recipes when people who aren't interested in git (like
me) are forced to learn how to use it.

I'll be summarising my experience in admin/notes tomorrow, since I now
have a (more or less) working setup.

And it'll be short, and won't mention the words "refs", "stash" or
"staging", but will just give the commands that you should use.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2014-11-14 15:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 22:44 bug#19049: 25.0.50; emacs-repository-get-version doesn't work with git Ulrich Mueller
2014-11-14  4:01 ` Lars Magne Ingebrigtsen
2014-11-14  4:06   ` Lars Magne Ingebrigtsen
2014-11-14  7:19     ` Ulrich Mueller
2014-11-14  7:39       ` Eli Zaretskii
2014-11-14  8:07         ` Ulrich Mueller
2014-11-14  6:24   ` Eli Zaretskii
2014-11-14 14:12     ` Lars Magne Ingebrigtsen
2014-11-14 14:17       ` Dmitry Gutov
2014-11-14 14:22         ` Lars Magne Ingebrigtsen
2014-11-14 14:25         ` Lars Magne Ingebrigtsen
2014-11-14 14:37           ` Dmitry Gutov
2014-11-14 14:41             ` Lars Magne Ingebrigtsen
2014-11-14 14:52             ` Eli Zaretskii
2014-11-14 14:58               ` Dmitry Gutov
2014-11-14 15:06                 ` Eli Zaretskii
2014-11-14 14:52           ` Eli Zaretskii
2014-11-14 14:50         ` Eli Zaretskii
2014-11-14 14:47       ` Eli Zaretskii
2014-11-14 14:59         ` Lars Magne Ingebrigtsen
2014-11-14 15:11           ` Eli Zaretskii
2014-11-14 15:16             ` Lars Magne Ingebrigtsen [this message]
2014-11-14 15:23               ` Eli Zaretskii
2014-11-14 15:26                 ` Eli Zaretskii

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=m3389lstg6.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=19049@debbugs.gnu.org \
    --cc=eliz@gnu.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://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).