From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: larsi@gnus.org, 19049@debbugs.gnu.org
Subject: bug#19049: 25.0.50; emacs-repository-get-version doesn't work with git
Date: Fri, 14 Nov 2014 17:06:31 +0200 [thread overview]
Message-ID: <838ujdizyg.fsf@gnu.org> (raw)
In-Reply-To: <54661879.8070708@yandex.ru>
> Date: Fri, 14 Nov 2014 16:58:01 +0200
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: larsi@gnus.org, 19049@debbugs.gnu.org
>
> Sorry, as a Git user, I'm quite used to doing some history rewriting
> before doing push. I suppose others will get used to it, too.
It's easy to get used, yes. It is _not_ easy to figure out for the
first time how to do it. If we had that in writing, we could just
point people there (and many would read out of their own initiative).
next prev parent reply other threads:[~2014-11-14 15:06 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 [this message]
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
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=838ujdizyg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19049@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.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).