unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
	bruce.connor.am@gmail.com, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master f9fabb2 2/2: Merge branch 'master' of	git.sv.gnu.org:/srv/git/emacs
Date: Thu, 28 May 2015 16:44:52 +0100	[thread overview]
Message-ID: <87egm07ll7.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <87617c3fq3.fsf@gmx.de> (Michael Albinus's message of "Thu, 28 May 2015 17:05:08 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:
> That's what I did, likely.
>
> However, the tip might give me a way to bring the git repo back to a
> stable state, with potential loosing of local changes. As long as I'm
> not fluent in solving merge conflicts, that's good to know.
>
>> OTOH, merge conflicts are nothing to be afraid of, the procedure to
>> handle them is simple and straightforward.  Michael (and every one
>> else here) should IMO master that simple procedure, instead of
>> avoiding it.
>>
>> In a dVCS, you cannot rely on being able to avoid merges all the time
>> anyway.  There are always races with other developers.
>
> If git would be more friendly to tell what happens ... why the hell I
> must take care on files I've never touched myself.


Perhaps the sensible way forward would be to push to a branch either on
or off the the main repo and then do a request pull. Much easier for
anyone scared of git (like me).

Of course, some one has to be able to answer the request, but then
having this set up would be no bad thing anyway, for those without
commit access, as well as those just scared.

Phil



  parent reply	other threads:[~2015-05-28 15:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150527165006.32357.80915@vcs.savannah.gnu.org>
     [not found] ` <E1YxeWz-0008TK-TD@vcs.savannah.gnu.org>
2015-05-28  2:40   ` [Emacs-diffs] master f9fabb2 2/2: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Stefan Monnier
2015-05-28  8:13     ` Michael Albinus
2015-05-28  9:27       ` Artur Malabarba
2015-05-28 10:05         ` Michael Albinus
2015-05-28 10:16           ` Andreas Schwab
2015-05-28 10:26             ` Michael Albinus
2015-05-28 16:55               ` Stefan Monnier
2015-05-28 14:46         ` Eli Zaretskii
2015-05-28 15:05           ` Michael Albinus
2015-05-28 15:26             ` Eli Zaretskii
2015-05-28 15:44             ` Phillip Lord [this message]
2015-05-28 16:24           ` Artur Malabarba
2015-05-28 17:02             ` Eli Zaretskii
2015-05-28 14:40       ` Eli Zaretskii
2015-05-28 15:00         ` Michael Albinus
2015-05-28 15:19           ` Eli Zaretskii
2015-05-28 15:52             ` Michael Albinus
2015-05-28 15:56               ` Dmitry Gutov
2015-05-28 16:52               ` Eli Zaretskii
2015-05-28 15:49           ` Andreas Schwab
2015-05-28 19:02           ` Stefan Monnier
2015-05-29  2:20             ` Yuri Khan

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=87egm07ll7.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=bruce.connor.am@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).