all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: David Engster <deng@randomsample.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: A simple git workflow for the rest of us
Date: Sun, 16 Nov 2014 15:42:49 +0100	[thread overview]
Message-ID: <m3lhnbfbpy.fsf@stories.gnus.org> (raw)
In-Reply-To: <87r3x3usd8.fsf@engster.org> (David Engster's message of "Sun, 16 Nov 2014 15:34:11 +0100")

David Engster <deng@randomsample.de> writes:

> I strongly suggest to change the default to something like 'simple',
> which will only update the current branch to the corresponding upstream
> branch with the same name. This was also made the new default in Git
> 2.x (way too late, but at least they changed it).
>
> You can set this globally by doing
>
>   git config --global push.default simple

I see; thanks.  Is there a way to set this for the Emacs repository
only, so that the simple git Emacs instructions doesn't affect what the
developer might otherwise be working on?  Or, since the default has
changed now, is this something that basically everybody wants, so it
really should be global?

> Note that 'simple' is only available since Git 1.7.11, and Debian stable
> still has 1.7.10. On older versions you can use 'upstream' or maybe
> 'current' (see 'git help config' to see the available options for
> 'push.default'), but I'd rather suggest to update Git from
> wheezy-backports.

For the instructions, I'd rather have a recipe that works for everybody
without installing newer git versions.  My git version has "upstream"
and "current" as possibilities...

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



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

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 16:09 A simple git workflow for the rest of us Lars Magne Ingebrigtsen
2014-11-15 16:38 ` Eli Zaretskii
2014-11-15 17:08   ` Lars Magne Ingebrigtsen
2014-11-16  2:57     ` Ted Zlatanov
2014-11-15 17:43   ` Achim Gratz
2014-11-15 18:04     ` Eli Zaretskii
2014-11-15 17:39 ` Achim Gratz
2014-11-15 17:47   ` Lars Magne Ingebrigtsen
2014-11-15 19:47     ` Karl Fogel
2014-11-16 19:05     ` Bill Wohler
2014-11-22  9:23     ` Steinar Bang
2014-11-22 13:35       ` Lars Magne Ingebrigtsen
2014-11-22 15:00         ` Steinar Bang
2014-11-22 15:26           ` Lars Magne Ingebrigtsen
2014-11-15 18:17   ` Andreas Schwab
2014-11-15 20:20   ` Kelvin White
2014-11-15 20:54     ` Kelvin White
2014-11-16 19:33   ` Bill Wohler
2014-11-16 19:43     ` Lars Magne Ingebrigtsen
2014-11-16 20:12       ` Ted Zlatanov
2014-11-16 20:19     ` Eli Zaretskii
2014-11-22  9:29     ` Steinar Bang
2014-11-23 18:28       ` Bill Wohler
2014-11-24 15:25         ` Sergey Organov
2014-11-15 19:08 ` Lars Magne Ingebrigtsen
2014-11-15 19:46   ` Andreas Schwab
2014-11-16 14:13     ` Lars Magne Ingebrigtsen
2014-11-16 14:34       ` David Engster
2014-11-16 14:42         ` Lars Magne Ingebrigtsen [this message]
2014-11-16 14:50           ` David Engster
2014-11-16 14:54             ` Lars Magne Ingebrigtsen
2014-11-16 15:19             ` David Kastrup
2014-11-16 14:36       ` Achim Gratz
2014-11-16  2:15 ` Glenn Morris

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=m3lhnbfbpy.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=deng@randomsample.de \
    --cc=emacs-devel@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.