From: Markus Elfring <Markus.Elfring@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Clarifications for merge workflows
Date: Thu, 11 Mar 2010 14:02:04 +0100 [thread overview]
Message-ID: <4B98E9CC.9000700@web.de> (raw)
In-Reply-To: <7v63532h82.fsf@alter.siamese.dyndns.org>
Thanks for your explanation.
> And then the procedure to publish the result out, whether it is what I did
> myself, or what I helped to integrate into my history from others, is the
> same. I push the result out from that "local" place to the "public" one.
Does any observable difference exist if the data synchronisation would be
performed in the other direction?
> Of course, if you are always working on that "server", the fact that you
> are always working there makes it the most convenient place to do all of
> your work for you.
I guess that it matters a bit if the published repository "SHARE" is the leading
and authoritative storage location.
Regards,
Markus
prev parent reply other threads:[~2010-03-11 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 11:12 Clarifications for merge workflows Markus Elfring
2010-03-11 12:08 ` Junio C Hamano
2010-03-11 13:02 ` Markus Elfring [this message]
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=4B98E9CC.9000700@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
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 NNTP newsgroup(s).