From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, David Engster <deng@randomsample.de>,
emacs-devel@gnu.org
Subject: Re: Git question: specify branches to push
Date: Thu, 27 Nov 2014 20:38:40 +0100 [thread overview]
Message-ID: <87d288o2m7.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <838uiwo9a8.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Nov 2014 19:14:39 +0200")
On Thu, 27 Nov 2014 19:14:39 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: David Engster <deng@randomsample.de>
>> Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, stephen.berman@gmx.net,
>> emacs-devel@gnu.org
>> Date: Thu, 27 Nov 2014 18:04:49 +0100
>>
>> Eli Zaretskii writes:
>> >> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
>> >> Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
>> >> Date: Thu, 27 Nov 2014 17:43:38 +0100
>> >>
>> >> > I use 'simple', not 'current', FWIW. Its advantage (among others) is
>> >> > that it's the default in Git 2.x.
>> >>
>> >> "simple" is not supported in older versions of git
>> >
>> > Older than what version?
>>
>> 1.7.11. (Debian ships with 1.7.10.)
>
> Thanks. Of course, the relevant question is what version does Stephen
> have.
git version 1.8.4.5
Steve Berman
next prev parent reply other threads:[~2014-11-27 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 10:27 Git question: specify branches to push Stephen Berman
2014-11-27 10:30 ` Lars Magne Ingebrigtsen
2014-11-27 11:15 ` Stephen Berman
2014-11-27 16:19 ` Eli Zaretskii
2014-11-27 16:43 ` Lars Magne Ingebrigtsen
2014-11-27 16:45 ` Eli Zaretskii
2014-11-27 16:53 ` Lars Magne Ingebrigtsen
2015-04-18 6:04 ` Steinar Bang
2014-11-27 17:04 ` David Engster
2014-11-27 17:14 ` Eli Zaretskii
2014-11-27 19:38 ` Stephen Berman [this message]
2014-11-27 17:06 ` Andreas Schwab
2014-11-27 10:59 ` Lee Duhem
2014-11-28 10:35 ` Phillip Lord
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=87d288o2m7.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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.